Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93ea1a27e696fa00723a2bb43efbc53f6b318a0e7ee13c1f8ae14c402b353df0

Tx prefix hash: 5b3d82550f5bb0fca13e0d952038ad1a861643ce526f110b154ca3bf349c6490
Tx public key: 428e0299b3b4158cee40f24d5705400a6379b90c94a3c50ed4efe03f421e7bd2
Timestamp: 1732212910 Timestamp [UCT]: 2024-11-21 18:15:10 Age [y:d:h:m:s]: 00:002:12:40:17
Block: 1158710 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1807 RingCT/type: yes/0
Extra: 01428e0299b3b4158cee40f24d5705400a6379b90c94a3c50ed4efe03f421e7bd20211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 170eab26ca5d1cf3350032b72ad9f104aec0749eee58d0f370a8d39b72bd0ce7 0.600000000000 1644339 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": 1158720, "vin": [ { "gen": { "height": 1158710 } } ], "vout": [ { "amount": 600000000, "target": { "key": "170eab26ca5d1cf3350032b72ad9f104aec0749eee58d0f370a8d39b72bd0ce7" } } ], "extra": [ 1, 66, 142, 2, 153, 179, 180, 21, 140, 238, 64, 242, 77, 87, 5, 64, 10, 99, 121, 185, 12, 148, 163, 197, 14, 212, 239, 224, 63, 66, 30, 123, 210, 2, 17, 0, 0, 0, 5, 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