Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5fbc3cfc6a748f643f0027ea62db593c5f029b3e1912ea4c9f25612a40544757

Tx prefix hash: d7aff38e31d2b8e0e73161c768f3c9cefce81ee4367974ef70a8bfd0b2ca7542
Tx public key: dd8aee4a803adc8441ea90001b8881c8249378d4b00357a31ccddfa204b2bdfd
Timestamp: 1707404439 Timestamp [UCT]: 2024-02-08 15:00:39 Age [y:d:h:m:s]: 01:067:04:04:33
Block: 953127 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309058 RingCT/type: yes/0
Extra: 01dd8aee4a803adc8441ea90001b8881c8249378d4b00357a31ccddfa204b2bdfd02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ed3b31588ff57e5cd413e4161d91b4371326a659cb7fef1da52630d2d423b023 0.600000000000 1412295 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": 953137, "vin": [ { "gen": { "height": 953127 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ed3b31588ff57e5cd413e4161d91b4371326a659cb7fef1da52630d2d423b023" } } ], "extra": [ 1, 221, 138, 238, 74, 128, 58, 220, 132, 65, 234, 144, 0, 27, 136, 129, 200, 36, 147, 120, 212, 176, 3, 87, 163, 28, 205, 223, 162, 4, 178, 189, 253, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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