Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2bab0cca1bf83df27eeacc49086e7672b906e2d89f4d9d94f1be500da52c75aa

Tx prefix hash: 45ae72bf21001e018ce903fc64f6c5fec439e73e3ace77b1b5ab303b94b151d5
Tx public key: 8a150f034a726f0244bfc046f8cc38c51b6430781ad5278f8381c233c5b34f06
Timestamp: 1717188834 Timestamp [UCT]: 2024-05-31 20:53:54 Age [y:d:h:m:s]: 00:308:15:56:47
Block: 1034254 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220595 RingCT/type: yes/0
Extra: 018a150f034a726f0244bfc046f8cc38c51b6430781ad5278f8381c233c5b34f0602110000000b59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de273e20fb1fac737b79fc520a1e4ea655f75452b46f9c0704f238a3a296e29f 0.600000000000 1502751 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": 1034264, "vin": [ { "gen": { "height": 1034254 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de273e20fb1fac737b79fc520a1e4ea655f75452b46f9c0704f238a3a296e29f" } } ], "extra": [ 1, 138, 21, 15, 3, 74, 114, 111, 2, 68, 191, 192, 70, 248, 204, 56, 197, 27, 100, 48, 120, 26, 213, 39, 143, 131, 129, 194, 51, 197, 179, 79, 6, 2, 17, 0, 0, 0, 11, 89, 218, 211, 245, 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