Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1e257819b0daed322fafc0121deb995acf883bfd99e4c405cd5b19eff8155e5

Tx prefix hash: 99c3f131bef0ddd71fef0b63eefb0e40d050ecf5ca7aef92902d6706319f6025
Tx public key: e13efaa9616b1ee9a0c6fc039262d17955ce52f98d5bfea1e5e4d614672d2c12
Timestamp: 1597533290 Timestamp [UCT]: 2020-08-15 23:14:50 Age [y:d:h:m:s]: 04:096:10:14:51
Block: 126840 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1030183 RingCT/type: yes/0
Extra: 01e13efaa9616b1ee9a0c6fc039262d17955ce52f98d5bfea1e5e4d614672d2c120211000000048a2ee0d9000000000000000000

1 output(s) for total of 233.199250129000 dcy

stealth address amount amount idx
00: 2b6ef4315ae88c5eb2da60801dbe7bf2359bed9c391ba821fdf3f1d5aef612c9 233.199250129000 213870 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": 126850, "vin": [ { "gen": { "height": 126840 } } ], "vout": [ { "amount": 233199250129, "target": { "key": "2b6ef4315ae88c5eb2da60801dbe7bf2359bed9c391ba821fdf3f1d5aef612c9" } } ], "extra": [ 1, 225, 62, 250, 169, 97, 107, 30, 233, 160, 198, 252, 3, 146, 98, 209, 121, 85, 206, 82, 249, 141, 91, 254, 161, 229, 228, 214, 20, 103, 45, 44, 18, 2, 17, 0, 0, 0, 4, 138, 46, 224, 217, 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