Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31107789c6181b038072f8330fcfb013815d6a72f889bf4876ecd9a8efe92499

Tx prefix hash: 2f8ff7a7766632df30e89e04d6085e446f8ba87fa32d91c4cdeb7d6be861c72b
Tx public key: 04a7ad15e662749c01b380cdb17befa6f313063e905b2095e6cf07a6f34fb63d
Timestamp: 1735556461 Timestamp [UCT]: 2024-12-30 11:01:01 Age [y:d:h:m:s]: 00:109:03:30:20
Block: 1186392 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77812 RingCT/type: yes/0
Extra: 0104a7ad15e662749c01b380cdb17befa6f313063e905b2095e6cf07a6f34fb63d021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96d84abdda28d19f6d012d7b9a87e84f813b0d8f33c9841b069de411c6507577 0.600000000000 1672873 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": 1186402, "vin": [ { "gen": { "height": 1186392 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96d84abdda28d19f6d012d7b9a87e84f813b0d8f33c9841b069de411c6507577" } } ], "extra": [ 1, 4, 167, 173, 21, 230, 98, 116, 156, 1, 179, 128, 205, 177, 123, 239, 166, 243, 19, 6, 62, 144, 91, 32, 149, 230, 207, 7, 166, 243, 79, 182, 61, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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