Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ece3d281e7590b29e7491685ae3c77997c37875d4df7dc0b3f68ed5929fc298d

Tx prefix hash: 6fda3ad6e93b9d4e5b69f3a0d018c9df8834a60fc07182460113b19d6e5d302b
Tx public key: bdc724c915093c54ce9c76167ca076e8eacfe3238d6075e4f060e517e815598c
Timestamp: 1574107790 Timestamp [UCT]: 2019-11-18 20:09:50 Age [y:d:h:m:s]: 05:348:13:27:02
Block: 12129 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1389718 RingCT/type: yes/0
Extra: 01bdc724c915093c54ce9c76167ca076e8eacfe3238d6075e4f060e517e815598c02110000000166a80d00000000000000000000

1 output(s) for total of 559.515956435000 dcy

stealth address amount amount idx
00: a97ce1daeb35b2673e2fd629efe616a763e1b2a4b7a5f786882ecf882f5eebfd 559.515956435000 13216 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": 12139, "vin": [ { "gen": { "height": 12129 } } ], "vout": [ { "amount": 559515956435, "target": { "key": "a97ce1daeb35b2673e2fd629efe616a763e1b2a4b7a5f786882ecf882f5eebfd" } } ], "extra": [ 1, 189, 199, 36, 201, 21, 9, 60, 84, 206, 156, 118, 22, 124, 160, 118, 232, 234, 207, 227, 35, 141, 96, 117, 228, 240, 96, 229, 23, 232, 21, 89, 140, 2, 17, 0, 0, 0, 1, 102, 168, 13, 0, 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