Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0a3688c279c72d3604148fd7d6dbd1d47762921b4ffc90fb9534cc665bba33f

Tx prefix hash: 453c46855a79fed12b850d460ec2a5a3bca1950cda697a31b145c2d22594d713
Tx public key: df018588a1c43907f7fd6076415c7315a8c6bf5805fd38f7da64158b1c5b84cd
Timestamp: 1704497054 Timestamp [UCT]: 2024-01-05 23:24:14 Age [y:d:h:m:s]: 01:305:06:31:25
Block: 929014 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 476998 RingCT/type: yes/0
Extra: 01df018588a1c43907f7fd6076415c7315a8c6bf5805fd38f7da64158b1c5b84cd02110000000e0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 670efc60e0ba2cdc2b6582add57f575048b37584105f0ee1d516f001e6f7c2f6 0.600000000000 1386882 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": 929024, "vin": [ { "gen": { "height": 929014 } } ], "vout": [ { "amount": 600000000, "target": { "key": "670efc60e0ba2cdc2b6582add57f575048b37584105f0ee1d516f001e6f7c2f6" } } ], "extra": [ 1, 223, 1, 133, 136, 161, 196, 57, 7, 247, 253, 96, 118, 65, 92, 115, 21, 168, 198, 191, 88, 5, 253, 56, 247, 218, 100, 21, 139, 28, 91, 132, 205, 2, 17, 0, 0, 0, 14, 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