Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3de1408f17e7761086c6fcd2538c4ec0a7abb3ccf6e2de67a7eb8ba2bf5518c7

Tx prefix hash: d969a8be50eea84f9805deba5959317605dcb43df9cffa2a65efae8cdebf94d1
Tx public key: 66a637380933f608b175d3b0ecc11860100f1d3a5258df794059083d5e128ecf
Timestamp: 1742234530 Timestamp [UCT]: 2025-03-17 18:02:10 Age [y:d:h:m:s]: 00:294:02:22:56
Block: 1241438 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207994 RingCT/type: yes/0
Extra: 0166a637380933f608b175d3b0ecc11860100f1d3a5258df794059083d5e128ecf02110000000c007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2954c150a3b632cf0dc55cfbf2cb34e8317d7f9fd1177076a99d5e33bc3b9a6d 0.600000000000 1728411 of 15

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": 1241448, "vin": [ { "gen": { "height": 1241438 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2954c150a3b632cf0dc55cfbf2cb34e8317d7f9fd1177076a99d5e33bc3b9a6d" } } ], "extra": [ 1, 102, 166, 55, 56, 9, 51, 246, 8, 177, 117, 211, 176, 236, 193, 24, 96, 16, 15, 29, 58, 82, 88, 223, 121, 64, 89, 8, 61, 94, 18, 142, 207, 2, 17, 0, 0, 0, 12, 0, 127, 151, 138, 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