Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 336fc7e046a9cf1c978a38459e174db75dee3181af43e1ca8559f709a4bc0ed2

Tx prefix hash: 516f42feb64043dede9d8695f6430c4790c5939cef046b0875ed86a969c502bf
Tx public key: 19622a037af3013180c5594a48f262faef26d90af97096a2b03bb6a7a29563ca
Timestamp: 1581316230 Timestamp [UCT]: 2020-02-10 06:30:30 Age [y:d:h:m:s]: 05:268:20:38:45
Block: 61764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1342745 RingCT/type: yes/0
Extra: 0119622a037af3013180c5594a48f262faef26d90af97096a2b03bb6a7a29563ca0211000000058a2ee0d9000000000000000000

1 output(s) for total of 383.134309232000 dcy

stealth address amount amount idx
00: 1c7893a1709cb33c2a7a0eddbf407ce951719b6440335d3fbc277a10c51ce4d1 383.134309232000 113911 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": 61774, "vin": [ { "gen": { "height": 61764 } } ], "vout": [ { "amount": 383134309232, "target": { "key": "1c7893a1709cb33c2a7a0eddbf407ce951719b6440335d3fbc277a10c51ce4d1" } } ], "extra": [ 1, 25, 98, 42, 3, 122, 243, 1, 49, 128, 197, 89, 74, 72, 242, 98, 250, 239, 38, 217, 10, 249, 112, 150, 162, 176, 59, 182, 167, 162, 149, 99, 202, 2, 17, 0, 0, 0, 5, 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