Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 12f5ea6d5c8c41daabc13109914487342bb0854cb44c9800d51ecafb02f7d827

Tx prefix hash: 910103a4632405fe5fa02a79c1ed59c2924ce82c35d41ee5e4a7c4b985623154
Tx public key: b0e1437cf41d43cbbd3ff72fe747f3e6aec9d4e2d4a953b395acdd3ad4bf28ba
Timestamp: 1733897894 Timestamp [UCT]: 2024-12-11 06:18:14 Age [y:d:h:m:s]: 00:017:16:08:35
Block: 1172685 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 12620 RingCT/type: yes/0
Extra: 01b0e1437cf41d43cbbd3ff72fe747f3e6aec9d4e2d4a953b395acdd3ad4bf28ba021100000001c7ca14c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0489ea84d45a687fc91b14c51e323263cc8432434084ce19327de353d6944f4 0.600000000000 1658610 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1172695, "vin": [ { "gen": { "height": 1172685 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0489ea84d45a687fc91b14c51e323263cc8432434084ce19327de353d6944f4" } } ], "extra": [ 1, 176, 225, 67, 124, 244, 29, 67, 203, 189, 63, 247, 47, 231, 71, 243, 230, 174, 201, 212, 226, 212, 169, 83, 179, 149, 172, 221, 58, 212, 191, 40, 186, 2, 17, 0, 0, 0, 1, 199, 202, 20, 193, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8