Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6b8f80c2990bed3d806f2b639a10811872a142a996446bb8eb26d5de28124bb

Tx prefix hash: f71c3ebd632cdb59948a6379ee4d9c06053ecad6fd6302f91598e52ca3c054ce
Tx public key: 7b7a2141e6538093af90ea6338b77432584a8cfd81cdc13dce6ff1545f7d1a3e
Timestamp: 1715466367 Timestamp [UCT]: 2024-05-11 22:26:07 Age [y:d:h:m:s]: 01:019:13:57:29
Block: 1019999 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274913 RingCT/type: yes/0
Extra: 017b7a2141e6538093af90ea6338b77432584a8cfd81cdc13dce6ff1545f7d1a3e02110000000341ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f21877cee1333e811a4cf34f41a6dce0be086412d65a3f76e8a99e56e119e442 0.600000000000 1484058 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": 1020009, "vin": [ { "gen": { "height": 1019999 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f21877cee1333e811a4cf34f41a6dce0be086412d65a3f76e8a99e56e119e442" } } ], "extra": [ 1, 123, 122, 33, 65, 230, 83, 128, 147, 175, 144, 234, 99, 56, 183, 116, 50, 88, 74, 140, 253, 129, 205, 193, 61, 206, 111, 241, 84, 95, 125, 26, 62, 2, 17, 0, 0, 0, 3, 65, 238, 28, 155, 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