Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7fdfd5e087594f234d7c2efcb3eadf342fe8cf4d6cc7e24143c9bf2d0aca5c95

Tx prefix hash: 5d56177c487a100ca30657110e66dac99caf848058c0ccc3a587dca328375036
Tx public key: 92cb3dd8d8a40f2e633f6366c8a0a41ed3a679cf6098b7b7ec52cf9cfea76e2d
Timestamp: 1635126235 Timestamp [UCT]: 2021-10-25 01:43:55 Age [y:d:h:m:s]: 03:141:10:46:36
Block: 359867 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 879263 RingCT/type: yes/0
Extra: 0192cb3dd8d8a40f2e633f6366c8a0a41ed3a679cf6098b7b7ec52cf9cfea76e2d0211000000107e786c8c000000000000000000

1 output(s) for total of 39.410473271000 dcy

stealth address amount amount idx
00: 05c0fe766cc44b5c031f85ef2ec8a1375fcb3cc298a40041feb7a3506f56a4ea 39.410473271000 732642 of 0

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": 359877, "vin": [ { "gen": { "height": 359867 } } ], "vout": [ { "amount": 39410473271, "target": { "key": "05c0fe766cc44b5c031f85ef2ec8a1375fcb3cc298a40041feb7a3506f56a4ea" } } ], "extra": [ 1, 146, 203, 61, 216, 216, 164, 15, 46, 99, 63, 99, 102, 200, 160, 164, 30, 211, 166, 121, 207, 96, 152, 183, 183, 236, 82, 207, 156, 254, 167, 110, 45, 2, 17, 0, 0, 0, 16, 126, 120, 108, 140, 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