Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 362b7b1c6fa5bbafa22b29867b0a0ff7f40a0dcf0d4464e43ca3eda22aa4c5d7

Tx prefix hash: cf6adfdb092e984d51e6ebb7ba5aafb4fe410e6ba33bd7efae1bdfa3fe07efad
Tx public key: 49e94da4a4edc3fef546fc9aea00eb443e483ba37733ee11fb06e96fe6f3aecf
Timestamp: 1578925093 Timestamp [UCT]: 2020-01-13 14:18:13 Age [y:d:h:m:s]: 05:146:03:13:23
Block: 44686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1254659 RingCT/type: yes/0
Extra: 0149e94da4a4edc3fef546fc9aea00eb443e483ba37733ee11fb06e96fe6f3aecf021100000027391a8d0e000000000000000000

1 output(s) for total of 436.453090171000 dcy

stealth address amount amount idx
00: f7c5de00709d63360a8a87befdc7b16f376826cd009c04d7875bb8429a87c2dc 436.453090171000 81395 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": 44696, "vin": [ { "gen": { "height": 44686 } } ], "vout": [ { "amount": 436453090171, "target": { "key": "f7c5de00709d63360a8a87befdc7b16f376826cd009c04d7875bb8429a87c2dc" } } ], "extra": [ 1, 73, 233, 77, 164, 164, 237, 195, 254, 245, 70, 252, 154, 234, 0, 235, 68, 62, 72, 59, 163, 119, 51, 238, 17, 251, 6, 233, 111, 230, 243, 174, 207, 2, 17, 0, 0, 0, 39, 57, 26, 141, 14, 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