Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 240df45fc6934b5db0528dc6b24f4c670fdc0f974ff0083940dd38b7eef86df3

Tx prefix hash: b795d23c53ebf9403bba51d351df5b4ffd155db4b117297033ec60aeb04f4f43
Tx public key: 70dbac85afef5d93b3950d0d1fc24949ac1c12ac5c6783a5224e88ca38919ae1
Timestamp: 1723415250 Timestamp [UCT]: 2024-08-11 22:27:30 Age [y:d:h:m:s]: 00:310:08:53:30
Block: 1085866 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221631 RingCT/type: yes/0
Extra: 0170dbac85afef5d93b3950d0d1fc24949ac1c12ac5c6783a5224e88ca38919ae1021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6de7d263f926556edaca9abf767a4fb51b2dfc6fc5a334313229cb7e7962e6a8 0.600000000000 1560457 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": 1085876, "vin": [ { "gen": { "height": 1085866 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6de7d263f926556edaca9abf767a4fb51b2dfc6fc5a334313229cb7e7962e6a8" } } ], "extra": [ 1, 112, 219, 172, 133, 175, 239, 93, 147, 179, 149, 13, 13, 31, 194, 73, 73, 172, 28, 18, 172, 92, 103, 131, 165, 34, 78, 136, 202, 56, 145, 154, 225, 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