Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8fb17663991755e83662606f624b8887a4482b577993b7cc000e082794ab052a

Tx prefix hash: d2aac47940350b622f3d40506607199129c41a4c532b31d81825a99d33e6c731
Tx public key: 536ab50e924a5d9b2945c48fa33d1e4a5c36441c11e662a9e16e5d93ad214bd2
Timestamp: 1720093249 Timestamp [UCT]: 2024-07-04 11:40:49 Age [y:d:h:m:s]: 00:272:04:54:10
Block: 1058326 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194487 RingCT/type: yes/0
Extra: 01536ab50e924a5d9b2945c48fa33d1e4a5c36441c11e662a9e16e5d93ad214bd20211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b355372a37760d53f809f93bf4bfc9fdb4b75d0a9f3f668c36ba2b331d4f4f5 0.600000000000 1528779 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": 1058336, "vin": [ { "gen": { "height": 1058326 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b355372a37760d53f809f93bf4bfc9fdb4b75d0a9f3f668c36ba2b331d4f4f5" } } ], "extra": [ 1, 83, 106, 181, 14, 146, 74, 93, 155, 41, 69, 196, 143, 163, 61, 30, 74, 92, 54, 68, 28, 17, 230, 98, 169, 225, 110, 93, 147, 173, 33, 75, 210, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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