Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cc4ad0ca1a073f223206b6fdff4d4346c4df960307e4d78736e79f19e31c836

Tx prefix hash: a5fa9e63ac704b3d5b0c9d0289f9afc868986c1204ac83e244b84e3814624d00
Tx public key: ce9812329a8c724585fe157c8eac33703ae9443ac11c100939a32b250079bdb8
Timestamp: 1695642272 Timestamp [UCT]: 2023-09-25 11:44:32 Age [y:d:h:m:s]: 01:156:07:00:08
Block: 855817 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372730 RingCT/type: yes/0
Extra: 01ce9812329a8c724585fe157c8eac33703ae9443ac11c100939a32b250079bdb802110000000575e3f0e9000000000000000000

1 output(s) for total of 0.896031052000 dcy

stealth address amount amount idx
00: 2bfda548c67aa4fae4f507918a564b2d04af9646eb11bc4b8a2d590b4266f42c 0.896031052000 1309861 of 0

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": 855827, "vin": [ { "gen": { "height": 855817 } } ], "vout": [ { "amount": 896031052, "target": { "key": "2bfda548c67aa4fae4f507918a564b2d04af9646eb11bc4b8a2d590b4266f42c" } } ], "extra": [ 1, 206, 152, 18, 50, 154, 140, 114, 69, 133, 254, 21, 124, 142, 172, 51, 112, 58, 233, 68, 58, 193, 28, 16, 9, 57, 163, 43, 37, 0, 121, 189, 184, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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