Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ea5576a9834f0cc71d321086af6240fcba06420184c6f618add36b854a546f3

Tx prefix hash: 45436f47c13295e741e47ff502ec04f46e98996ed3be2f0ae62e9802e1f2c05c
Tx public key: f6a56d768d743415d9d90bbcb2b5d2a81ee17f4cad30ec69c4a4ad71fa3b5bd8
Timestamp: 1717725725 Timestamp [UCT]: 2024-06-07 02:02:05 Age [y:d:h:m:s]: 01:156:22:41:45
Block: 1038699 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 370747 RingCT/type: yes/0
Extra: 01f6a56d768d743415d9d90bbcb2b5d2a81ee17f4cad30ec69c4a4ad71fa3b5bd80211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 542c1264bf71187b412958d3e6890686847664f9c734dd6b1e25be4f3b539ee5 0.600000000000 1507260 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": 1038709, "vin": [ { "gen": { "height": 1038699 } } ], "vout": [ { "amount": 600000000, "target": { "key": "542c1264bf71187b412958d3e6890686847664f9c734dd6b1e25be4f3b539ee5" } } ], "extra": [ 1, 246, 165, 109, 118, 141, 116, 52, 21, 217, 217, 11, 188, 178, 181, 210, 168, 30, 225, 127, 76, 173, 48, 236, 105, 196, 164, 173, 113, 250, 59, 91, 216, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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