Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c58d1af1fb3fccfaed96a582e876183ec075cc78342b020a7c14d2efed0f6ae8

Tx prefix hash: ff97edf5e73426c8c0cac782c3631397ac5b1ccb1165085b571f5cc7cf6b5074
Tx public key: 16a7b327d949260c05168b3b0264652a33a8edc4dfa3a829ab736cb50dd8e2d8
Timestamp: 1720386888 Timestamp [UCT]: 2024-07-07 21:14:48 Age [y:d:h:m:s]: 00:199:06:51:55
Block: 1060763 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142553 RingCT/type: yes/0
Extra: 0116a7b327d949260c05168b3b0264652a33a8edc4dfa3a829ab736cb50dd8e2d8021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 81c3d679ce016983e09419d601b366cbaca65fc52e0987ad473ca5e158a6fc8b 0.600000000000 1531248 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": 1060773, "vin": [ { "gen": { "height": 1060763 } } ], "vout": [ { "amount": 600000000, "target": { "key": "81c3d679ce016983e09419d601b366cbaca65fc52e0987ad473ca5e158a6fc8b" } } ], "extra": [ 1, 22, 167, 179, 39, 217, 73, 38, 12, 5, 22, 139, 59, 2, 100, 101, 42, 51, 168, 237, 196, 223, 163, 168, 41, 171, 115, 108, 181, 13, 216, 226, 216, 2, 17, 0, 0, 0, 9, 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