Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28e9b2d6ab507cd760a03162aa00198be8ea740319c737b59030b6f0eb700921

Tx prefix hash: 16d7d8117cb38a682b9126b82f2bd37ff5b750bc5a6c6fdb1162e0979a2ae0d5
Tx public key: 48dd2c256ea1fc3485d5bdeef4ce47f6e76a313851163c3fc6bee24a189e1684
Timestamp: 1727937443 Timestamp [UCT]: 2024-10-03 06:37:23 Age [y:d:h:m:s]: 01:062:08:07:06
Block: 1123365 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302984 RingCT/type: yes/0
Extra: 0148dd2c256ea1fc3485d5bdeef4ce47f6e76a313851163c3fc6bee24a189e1684021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 30859e54fe189c3f32efcbb8b16c4e094a1fde038e528afa53e16ae9ede1d723 0.600000000000 1605898 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": 1123375, "vin": [ { "gen": { "height": 1123365 } } ], "vout": [ { "amount": 600000000, "target": { "key": "30859e54fe189c3f32efcbb8b16c4e094a1fde038e528afa53e16ae9ede1d723" } } ], "extra": [ 1, 72, 221, 44, 37, 110, 161, 252, 52, 133, 213, 189, 238, 244, 206, 71, 246, 231, 106, 49, 56, 81, 22, 60, 63, 198, 190, 226, 74, 24, 158, 22, 132, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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