Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1eec251ffc0dcd449a599de7710c8349768c0dd8a53a9d374eb4b42317bb8d60

Tx prefix hash: b2d70af40693f9d3973e5ebd071f0a8516eed684dba50fd28a3931ed632b2dcd
Tx public key: 4bc5f897a74162460470b86f3ad6dcff490aab63217b38b2d671fccc1109bcf9
Timestamp: 1577027645 Timestamp [UCT]: 2019-12-22 15:14:05 Age [y:d:h:m:s]: 04:329:13:25:59
Block: 29665 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1124340 RingCT/type: yes/0
Extra: 014bc5f897a74162460470b86f3ad6dcff490aab63217b38b2d671fccc1109bcf90211000000078a2ee0d9000000000000000000

1 output(s) for total of 489.450079346000 dcy

stealth address amount amount idx
00: 19ec749daba19abf667a06129c2d0524e0e00e11158677d613ae82c4082b10f6 489.450079346000 48827 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": 29675, "vin": [ { "gen": { "height": 29665 } } ], "vout": [ { "amount": 489450079346, "target": { "key": "19ec749daba19abf667a06129c2d0524e0e00e11158677d613ae82c4082b10f6" } } ], "extra": [ 1, 75, 197, 248, 151, 167, 65, 98, 70, 4, 112, 184, 111, 58, 214, 220, 255, 73, 10, 171, 99, 33, 123, 56, 178, 214, 113, 252, 204, 17, 9, 188, 249, 2, 17, 0, 0, 0, 7, 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