Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67226d83d7047b36395b17d261ee2ecd8fd59cd32acbede93469c7501a588f57

Tx prefix hash: a1ada5362d7612d990ae78c4b63344a55e2e7caa39b455e8ea8db92a776deb34
Tx public key: 165800c00912da15cf99fab25cfbbd73c4773b68e4e5d1b4e2a5f64cf13b9d0c
Timestamp: 1732066727 Timestamp [UCT]: 2024-11-20 01:38:47 Age [y:d:h:m:s]: 00:003:20:22:32
Block: 1157504 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2745 RingCT/type: yes/0
Extra: 01165800c00912da15cf99fab25cfbbd73c4773b68e4e5d1b4e2a5f64cf13b9d0c021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 27e36f32d7d615e0f2d8eaf2797797e8f5e80daeeeeb0104f230abcd6d6f6c99 0.600000000000 1643127 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": 1157514, "vin": [ { "gen": { "height": 1157504 } } ], "vout": [ { "amount": 600000000, "target": { "key": "27e36f32d7d615e0f2d8eaf2797797e8f5e80daeeeeb0104f230abcd6d6f6c99" } } ], "extra": [ 1, 22, 88, 0, 192, 9, 18, 218, 21, 207, 153, 250, 178, 92, 251, 189, 115, 196, 119, 59, 104, 228, 229, 209, 180, 226, 165, 246, 76, 241, 59, 157, 12, 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