Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a304ce1f2c86efbaa9a43aad3e78f4e5264b0623a71bf92d894a8da3ad7164b4

Tx prefix hash: d749aa31dac8b7e5f841e2fc5b7bb4d37820e36c8abce3fef13f071994bce12c
Tx public key: 4f353fb0350879a856b95652a7a992fedc822ae447bbfa67dd08fc8a66567727
Timestamp: 1720539660 Timestamp [UCT]: 2024-07-09 15:41:00 Age [y:d:h:m:s]: 00:287:17:33:31
Block: 1062033 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205578 RingCT/type: yes/0
Extra: 014f353fb0350879a856b95652a7a992fedc822ae447bbfa67dd08fc8a6656772702110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21e6c2c3b2baec0bdce529a1a75bef0e0d9d94cc16289323cdb787fd61312cfe 0.600000000000 1532534 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": 1062043, "vin": [ { "gen": { "height": 1062033 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21e6c2c3b2baec0bdce529a1a75bef0e0d9d94cc16289323cdb787fd61312cfe" } } ], "extra": [ 1, 79, 53, 63, 176, 53, 8, 121, 168, 86, 185, 86, 82, 167, 169, 146, 254, 220, 130, 42, 228, 71, 187, 250, 103, 221, 8, 252, 138, 102, 86, 119, 39, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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