Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ff569573ea7cf4775c610d10808ba0015a1b7cea29930c4ccd9c05e2b8dd0d5

Tx prefix hash: 095218712633575a7839756856d863ea69cf49d0bd54b435fc8a4b298a09bce9
Tx public key: 059e944ea4bf0a592dee1cb62f642c731a0d41a1b05387d7c3b4d9ee5dfb9c41
Timestamp: 1731585917 Timestamp [UCT]: 2024-11-14 12:05:17 Age [y:d:h:m:s]: 01:038:17:42:15
Block: 1153517 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286146 RingCT/type: yes/0
Extra: 01059e944ea4bf0a592dee1cb62f642c731a0d41a1b05387d7c3b4d9ee5dfb9c41021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ccdb705ceffb06fe90bc7c9cfba5ff5a1dc042e9aaa6a3ec31cd1e2a9d340f0d 0.600000000000 1639126 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": 1153527, "vin": [ { "gen": { "height": 1153517 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ccdb705ceffb06fe90bc7c9cfba5ff5a1dc042e9aaa6a3ec31cd1e2a9d340f0d" } } ], "extra": [ 1, 5, 158, 148, 78, 164, 191, 10, 89, 45, 238, 28, 182, 47, 100, 44, 115, 26, 13, 65, 161, 176, 83, 135, 215, 195, 180, 217, 238, 93, 251, 156, 65, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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