Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db53b495571b925e7bb5705a6c4e18f6caf06f293bff213e95e653b5fdb64c06

Tx prefix hash: 8a9872898b1d8923831318c018ca6ec0ab496ee535b6291c8a2f1b9c2787f95f
Tx public key: 82b843e35af153f0cf11a54c5acc117299f9fc46eb1d1cac0bf84a6031b9f343
Timestamp: 1702954734 Timestamp [UCT]: 2023-12-19 02:58:54 Age [y:d:h:m:s]: 01:326:04:43:47
Block: 916250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 491969 RingCT/type: yes/0
Extra: 0182b843e35af153f0cf11a54c5acc117299f9fc46eb1d1cac0bf84a6031b9f34302110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe03c57b876bf0454ecb728d7eda68a55333beffed7883ed8535620e5c561a7b 0.600000000000 1373734 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": 916260, "vin": [ { "gen": { "height": 916250 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe03c57b876bf0454ecb728d7eda68a55333beffed7883ed8535620e5c561a7b" } } ], "extra": [ 1, 130, 184, 67, 227, 90, 241, 83, 240, 207, 17, 165, 76, 90, 204, 17, 114, 153, 249, 252, 70, 235, 29, 28, 172, 11, 248, 74, 96, 49, 185, 243, 67, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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