Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d92ab671012d3b30796e1cc3bcf8282dd943e1e505c32c16331f92c244e6aac9

Tx prefix hash: 5602fb1762ca10049b362c355130d8618b1bde28a403ee78bb67ff9cc818435a
Tx public key: 2fcd697c9e8a862b4761fef0c44fa9ade9f53a361f8868dcb315242a5cd010a9
Timestamp: 1733614244 Timestamp [UCT]: 2024-12-07 23:30:44 Age [y:d:h:m:s]: 00:155:23:20:29
Block: 1170328 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111282 RingCT/type: yes/0
Extra: 012fcd697c9e8a862b4761fef0c44fa9ade9f53a361f8868dcb315242a5cd010a90211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b240ef2c736103856804da58b0019710e40b9f40af622163901e9c03b0f0e7d 0.600000000000 1656057 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": 1170338, "vin": [ { "gen": { "height": 1170328 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b240ef2c736103856804da58b0019710e40b9f40af622163901e9c03b0f0e7d" } } ], "extra": [ 1, 47, 205, 105, 124, 158, 138, 134, 43, 71, 97, 254, 240, 196, 79, 169, 173, 233, 245, 58, 54, 31, 136, 104, 220, 179, 21, 36, 42, 92, 208, 16, 169, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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