Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e6a6d9f040125b00d4ba69d4846c06172b4a7d7c1e556fe6ad034615338fcf3

Tx prefix hash: fdf01bd24e01798510bd97eaedd1fc771c0dba9f92d6199fd94f5efd32767ac5
Tx public key: 1c6a702625a37b105e1de859e64e2b9359e6100881610f4779b1cacc55cc1cf8
Timestamp: 1574192610 Timestamp [UCT]: 2019-11-19 19:43:30 Age [y:d:h:m:s]: 05:009:01:48:34
Block: 12748 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1149635 RingCT/type: yes/0
Extra: 011c6a702625a37b105e1de859e64e2b9359e6100881610f4779b1cacc55cc1cf8021100000003ccefb800000000000000000000

1 output(s) for total of 556.879808629000 dcy

stealth address amount amount idx
00: 4fa55656a477969749d8bbbad5bd2fb9b68a668cfdcdb56dc341608c361a7f29 556.879808629000 14428 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": 12758, "vin": [ { "gen": { "height": 12748 } } ], "vout": [ { "amount": 556879808629, "target": { "key": "4fa55656a477969749d8bbbad5bd2fb9b68a668cfdcdb56dc341608c361a7f29" } } ], "extra": [ 1, 28, 106, 112, 38, 37, 163, 123, 16, 94, 29, 232, 89, 230, 78, 43, 147, 89, 230, 16, 8, 129, 97, 15, 71, 121, 177, 202, 204, 85, 204, 28, 248, 2, 17, 0, 0, 0, 3, 204, 239, 184, 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