Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9405031e79780d141a489f950a06e6574e111fffcb3828e36187f3e1dcb3c42

Tx prefix hash: 1e6f5643a630fb85d1ac980ec0e6f698dc70c1ceb58997b5dd1a390b16ab0c05
Tx public key: ad05b9af3436aa228da286b7d19c8aafc6796ba6f6416e29d661e233b2aee6da
Timestamp: 1734652756 Timestamp [UCT]: 2024-12-19 23:59:16 Age [y:d:h:m:s]: 00:100:12:50:43
Block: 1178946 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71606 RingCT/type: yes/0
Extra: 01ad05b9af3436aa228da286b7d19c8aafc6796ba6f6416e29d661e233b2aee6da021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c6aa8507b60029a37ee14b9d987593ca4f249d12bf1a5b47cbc14e545e22e43 0.600000000000 1665337 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": 1178956, "vin": [ { "gen": { "height": 1178946 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c6aa8507b60029a37ee14b9d987593ca4f249d12bf1a5b47cbc14e545e22e43" } } ], "extra": [ 1, 173, 5, 185, 175, 52, 54, 170, 34, 141, 162, 134, 183, 209, 156, 138, 175, 198, 121, 107, 166, 246, 65, 110, 41, 214, 97, 226, 51, 178, 174, 230, 218, 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