Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec4e8a4687d05ebacd583f38898c494225af1c5e31bc1a9af81595dd8dd5e903

Tx prefix hash: 4e5dc4de50d9747a453adfc1bdf18a0d50c9189be7ed6c08c7ba1708e782a0a2
Tx public key: f8ac68d26a8f6717930054266e318f1096c461d1c2c7a1ea0e3a4f44f6f5c122
Timestamp: 1738928594 Timestamp [UCT]: 2025-02-07 11:43:14 Age [y:d:h:m:s]: 00:285:20:18:15
Block: 1214053 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202054 RingCT/type: yes/0
Extra: 01f8ac68d26a8f6717930054266e318f1096c461d1c2c7a1ea0e3a4f44f6f5c1220211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 55ef0ceeae0a0902276dc2df5ec2c3e9aec1a2180ff878e1e65179bd32db6cad 0.600000000000 1700838 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": 1214063, "vin": [ { "gen": { "height": 1214053 } } ], "vout": [ { "amount": 600000000, "target": { "key": "55ef0ceeae0a0902276dc2df5ec2c3e9aec1a2180ff878e1e65179bd32db6cad" } } ], "extra": [ 1, 248, 172, 104, 210, 106, 143, 103, 23, 147, 0, 84, 38, 110, 49, 143, 16, 150, 196, 97, 209, 194, 199, 161, 234, 14, 58, 79, 68, 246, 245, 193, 34, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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