Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e26129ab7af6d39e994bac9081066c1c07a146314e5c66892eedb28fb5818ce4

Tx prefix hash: 64ad5ad6b43f5f9a9100098b3f793e6b9dfc49c7d9e40dd440b6fdf540bd6410
Tx public key: 57ba6754b456e426842b1aa7ff949e5db6d37f04a701856c0d6f2901fcd8aa89
Timestamp: 1731227101 Timestamp [UCT]: 2024-11-10 08:25:01 Age [y:d:h:m:s]: 00:165:17:01:21
Block: 1150541 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118279 RingCT/type: yes/0
Extra: 0157ba6754b456e426842b1aa7ff949e5db6d37f04a701856c0d6f2901fcd8aa89021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bfefe070f4d99c1631f1bbbf3a9a6253f62688fde779b8698e64a4e663960454 0.600000000000 1635884 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": 1150551, "vin": [ { "gen": { "height": 1150541 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bfefe070f4d99c1631f1bbbf3a9a6253f62688fde779b8698e64a4e663960454" } } ], "extra": [ 1, 87, 186, 103, 84, 180, 86, 228, 38, 132, 43, 26, 167, 255, 148, 158, 93, 182, 211, 127, 4, 167, 1, 133, 108, 13, 111, 41, 1, 252, 216, 170, 137, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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