Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 396f0432c10fb84b65fe1c391a76b2fa20e004b644e7f4cf4bea79c350e99785

Tx prefix hash: 2fda083389cff3c9cca64f7b3893ab9f818569bbf75cccc13cf8009181671851
Tx public key: cae300c4be03d7476d5a783025403f408a06ba7b841badd9d3d4184cba7592f4
Timestamp: 1575680181 Timestamp [UCT]: 2019-12-07 00:56:21 Age [y:d:h:m:s]: 05:160:18:57:39
Block: 22071 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0967 kB
Tx version: 2 No of confirmations: 1260896 RingCT/type: yes/0
Extra: 01cae300c4be03d7476d5a783025403f408a06ba7b841badd9d3d4184cba7592f4020d3930303100010000002590824d

1 output(s) for total of 518.645350338000 dcy

stealth address amount amount idx
00: b810123009c16ba92aea04540dc7b44c8c9dbf8c6a9d821ac86b620228110626 518.645350338000 34978 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": 22081, "vin": [ { "gen": { "height": 22071 } } ], "vout": [ { "amount": 518645350338, "target": { "key": "b810123009c16ba92aea04540dc7b44c8c9dbf8c6a9d821ac86b620228110626" } } ], "extra": [ 1, 202, 227, 0, 196, 190, 3, 215, 71, 109, 90, 120, 48, 37, 64, 63, 64, 138, 6, 186, 123, 132, 27, 173, 217, 211, 212, 24, 76, 186, 117, 146, 244, 2, 13, 57, 48, 48, 49, 0, 1, 0, 0, 0, 37, 144, 130, 77 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8