Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b09d199fc2d86a16b52fd5cfd2f33fc6e97f25b3591cf96dc2a5a9e8f0bff0d6

Tx prefix hash: 891271965b37015fc2b91f0a00d7ab1994cddf06d5a4bc70f7177c02bfb29c05
Tx public key: d7d10750461164f32f6e7e4940e8e90794c82885393eeab3bb3a60b73e59914a
Timestamp: 1609703666 Timestamp [UCT]: 2021-01-03 19:54:26 Age [y:d:h:m:s]: 04:097:20:04:27
Block: 174137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1084381 RingCT/type: yes/0
Extra: 01d7d10750461164f32f6e7e4940e8e90794c82885393eeab3bb3a60b73e59914a0211000000ea90ce5c0f000000000000000000

1 output(s) for total of 162.559550986000 dcy

stealth address amount amount idx
00: 0f2d9385c69b35a38cfdbed1ecc45e37a1412eda86feddbbdba465b2f690ba73 162.559550986000 331191 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": 174147, "vin": [ { "gen": { "height": 174137 } } ], "vout": [ { "amount": 162559550986, "target": { "key": "0f2d9385c69b35a38cfdbed1ecc45e37a1412eda86feddbbdba465b2f690ba73" } } ], "extra": [ 1, 215, 209, 7, 80, 70, 17, 100, 243, 47, 110, 126, 73, 64, 232, 233, 7, 148, 200, 40, 133, 57, 62, 234, 179, 187, 58, 96, 183, 62, 89, 145, 74, 2, 17, 0, 0, 0, 234, 144, 206, 92, 15, 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