Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c581504dc15219c09ce4005d23d8bfb346bad4eb457168ee84dc4ca4b083aea3

Tx prefix hash: 750b93f4fd54a38d6dc6f4c4307c48c83ed18ae98197957c51b67a3d15e07688
Tx public key: 072a776b2b0c90c72660cd48d64b56d7c0fa8502c5a1771ce37a0274e252a123
Timestamp: 1576643752 Timestamp [UCT]: 2019-12-18 04:35:52 Age [y:d:h:m:s]: 05:119:20:00:34
Block: 28383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1233248 RingCT/type: yes/0
Extra: 01072a776b2b0c90c72660cd48d64b56d7c0fa8502c5a1771ce37a0274e252a1230211000000559159db1e000000000000000000

1 output(s) for total of 494.260840440000 dcy

stealth address amount amount idx
00: e8e272558ddc6cb7243121f69cae48178d48a45f777a99cadb17063886ddf15a 494.260840440000 46927 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": 28393, "vin": [ { "gen": { "height": 28383 } } ], "vout": [ { "amount": 494260840440, "target": { "key": "e8e272558ddc6cb7243121f69cae48178d48a45f777a99cadb17063886ddf15a" } } ], "extra": [ 1, 7, 42, 119, 107, 43, 12, 144, 199, 38, 96, 205, 72, 214, 75, 86, 215, 192, 250, 133, 2, 197, 161, 119, 28, 227, 122, 2, 116, 226, 82, 161, 35, 2, 17, 0, 0, 0, 85, 145, 89, 219, 30, 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