Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33e94f2f6a34c6d15e285efbe0234f9410514e857377a99a2142b238f5d1767c

Tx prefix hash: 6974451bd21b466ee434e057f6e0a15e7b817339d049ea1ea22524837a209189
Tx public key: 3d7c48b414809de2667d299b5752870cf31d35f7b415fd1ec64aaa69a5e07bcf
Timestamp: 1733599484 Timestamp [UCT]: 2024-12-07 19:24:44 Age [y:d:h:m:s]: 00:221:09:19:15
Block: 1170198 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156987 RingCT/type: yes/0
Extra: 013d7c48b414809de2667d299b5752870cf31d35f7b415fd1ec64aaa69a5e07bcf0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 886e218277f4b6a1fe95a3194d1a56877b7c68fd61e43b1392ae20fec2e52261 0.600000000000 1655927 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": 1170208, "vin": [ { "gen": { "height": 1170198 } } ], "vout": [ { "amount": 600000000, "target": { "key": "886e218277f4b6a1fe95a3194d1a56877b7c68fd61e43b1392ae20fec2e52261" } } ], "extra": [ 1, 61, 124, 72, 180, 20, 128, 157, 226, 102, 125, 41, 155, 87, 82, 135, 12, 243, 29, 53, 247, 180, 21, 253, 30, 198, 74, 170, 105, 165, 224, 123, 207, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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