Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05b3a11f00beaee40f8353dd135c215a949d2471718f4cbe2de80f1175f34634

Tx prefix hash: fcc4d7cf43dbbe62525cc8f61e397e6d074ce2c5a64e0617f915fb1109494b02
Tx public key: 611de36d9e2b9d277b94056a8e5c9dcddecdca10cfcbc2c693214374ed734ed4
Timestamp: 1706738166 Timestamp [UCT]: 2024-01-31 21:56:06 Age [y:d:h:m:s]: 01:068:03:02:34
Block: 947593 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309762 RingCT/type: yes/0
Extra: 01611de36d9e2b9d277b94056a8e5c9dcddecdca10cfcbc2c693214374ed734ed40211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7cfc4f5e89bca3ce1ec7c2f6d7038e1bbfbabc471b5183fa8fa30e74914ecdac 0.600000000000 1405945 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": 947603, "vin": [ { "gen": { "height": 947593 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7cfc4f5e89bca3ce1ec7c2f6d7038e1bbfbabc471b5183fa8fa30e74914ecdac" } } ], "extra": [ 1, 97, 29, 227, 109, 158, 43, 157, 39, 123, 148, 5, 106, 142, 92, 157, 205, 222, 205, 202, 16, 207, 203, 194, 198, 147, 33, 67, 116, 237, 115, 78, 212, 2, 17, 0, 0, 0, 1, 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