Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49c48d9b0c165ba9ffbfade0f3634f914d9cf0e1cd70e4599a2b758cd4bece7c

Tx prefix hash: addde3cfc42815ad271afc2edf9e1eb2c4ba3c77ff8ec2aaccafc1f888b70d20
Tx public key: beabd435a76a7a0b63e0ddd3e51b45c2b9803dbfd83842922e553a2423c60511
Timestamp: 1706035450 Timestamp [UCT]: 2024-01-23 18:44:10 Age [y:d:h:m:s]: 01:033:02:50:22
Block: 941751 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284736 RingCT/type: yes/0
Extra: 01beabd435a76a7a0b63e0ddd3e51b45c2b9803dbfd83842922e553a2423c6051102110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 12bcc70b7aafb21c447664a8d71bb23db02b0255fc8c02f6d835aac36de75ded 0.600000000000 1399907 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": 941761, "vin": [ { "gen": { "height": 941751 } } ], "vout": [ { "amount": 600000000, "target": { "key": "12bcc70b7aafb21c447664a8d71bb23db02b0255fc8c02f6d835aac36de75ded" } } ], "extra": [ 1, 190, 171, 212, 53, 167, 106, 122, 11, 99, 224, 221, 211, 229, 27, 69, 194, 185, 128, 61, 191, 216, 56, 66, 146, 46, 85, 58, 36, 35, 198, 5, 17, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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