Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1986472781bdf7a7e0451671f413190477c76c12a061da134bf5adde18204a48

Tx prefix hash: 20aa4fc2174ef095c3c32922558a7e05657ea140ce3b2f9cb6fe11eee241a1a0
Tx public key: 5e441d225ec25be6b86870520a3a56c9a1d84d671ff8670da1c17b1d556effa3
Timestamp: 1580567427 Timestamp [UCT]: 2020-02-01 14:30:27 Age [y:d:h:m:s]: 04:299:12:55:44
Block: 56514 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1105338 RingCT/type: yes/0
Extra: 015e441d225ec25be6b86870520a3a56c9a1d84d671ff8670da1c17b1d556effa302110000000149b77a3d000000000000000000

1 output(s) for total of 398.801110251000 dcy

stealth address amount amount idx
00: 4b3936ee6e5848358221e1efa1cdd227ed8f42a27ffb0d6c88ec703658edade1 398.801110251000 104243 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": 56524, "vin": [ { "gen": { "height": 56514 } } ], "vout": [ { "amount": 398801110251, "target": { "key": "4b3936ee6e5848358221e1efa1cdd227ed8f42a27ffb0d6c88ec703658edade1" } } ], "extra": [ 1, 94, 68, 29, 34, 94, 194, 91, 230, 184, 104, 112, 82, 10, 58, 86, 201, 161, 216, 77, 103, 31, 248, 103, 13, 161, 193, 123, 29, 85, 110, 255, 163, 2, 17, 0, 0, 0, 1, 73, 183, 122, 61, 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