Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fda00ba59870caf42bcf309c01cede026b86e247007ad7c6474c253e6a12542c

Tx prefix hash: cbc19715733b3c89270e6b26531b186c408a6a977baf94dbc80346493caf3a72
Tx public key: 8c647884a4421f43f23066761c6a6d9b0aa794daca6cde3f5f61d0a77a4cd6c5
Timestamp: 1709287211 Timestamp [UCT]: 2024-03-01 10:00:11 Age [y:d:h:m:s]: 00:329:13:12:05
Block: 968750 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235845 RingCT/type: yes/0
Extra: 018c647884a4421f43f23066761c6a6d9b0aa794daca6cde3f5f61d0a77a4cd6c502110000000149a185bb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1382801f39b2bf950db964ca7196a2bd4d5131e1e9ef9c2dc058d859061e685 0.600000000000 1428573 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": 968760, "vin": [ { "gen": { "height": 968750 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1382801f39b2bf950db964ca7196a2bd4d5131e1e9ef9c2dc058d859061e685" } } ], "extra": [ 1, 140, 100, 120, 132, 164, 66, 31, 67, 242, 48, 102, 118, 28, 106, 109, 155, 10, 167, 148, 218, 202, 108, 222, 63, 95, 97, 208, 167, 122, 76, 214, 197, 2, 17, 0, 0, 0, 1, 73, 161, 133, 187, 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