Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5051294524de4251f8cc81fd75ea56914448491397a424ca789a466270c2733

Tx prefix hash: f302adf7c6735fa540f5555a5d25b496fc9c9d22ac66a3fdcaaebdac4c68e3c5
Tx public key: fca1dbae7e2f73b6cc8d42b774c31951f13c3d642c1824ca6d143a4a89fb344d
Timestamp: 1728230405 Timestamp [UCT]: 2024-10-06 16:00:05 Age [y:d:h:m:s]: 00:186:16:51:45
Block: 1125787 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133238 RingCT/type: yes/0
Extra: 01fca1dbae7e2f73b6cc8d42b774c31951f13c3d642c1824ca6d143a4a89fb344d02110000000f91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d9c4494725645aa2f496cc374b273cc01fbe774924a6e814ccbcb2bcd33e5ba 0.600000000000 1608538 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": 1125797, "vin": [ { "gen": { "height": 1125787 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d9c4494725645aa2f496cc374b273cc01fbe774924a6e814ccbcb2bcd33e5ba" } } ], "extra": [ 1, 252, 161, 219, 174, 126, 47, 115, 182, 204, 141, 66, 183, 116, 195, 25, 81, 241, 60, 61, 100, 44, 24, 36, 202, 109, 20, 58, 74, 137, 251, 52, 77, 2, 17, 0, 0, 0, 15, 145, 225, 60, 4, 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