Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c80cebdc0c86bc2333615c0da808c468a99a6767e369a0c48170c161878ad49

Tx prefix hash: b803a928b8cc08e3cbd013d9999c8dbdef238685dd410ab6e7a1ee3fab94e130
Tx public key: 0c5122fd6f40a6133c625c281ba6f1ab51ab295743eb21b037d9a6b67f30751c
Timestamp: 1745820228 Timestamp [UCT]: 2025-04-28 06:03:48 Age [y:d:h:m:s]: 00:037:17:28:50
Block: 1271114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 26986 RingCT/type: yes/0
Extra: 010c5122fd6f40a6133c625c281ba6f1ab51ab295743eb21b037d9a6b67f30751c0211000000081f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9fff00f4255221b79fcf47622a8c750dbd7071d554513ce8f68e5dce30e78788 0.600000000000 1758363 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": 1271124, "vin": [ { "gen": { "height": 1271114 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9fff00f4255221b79fcf47622a8c750dbd7071d554513ce8f68e5dce30e78788" } } ], "extra": [ 1, 12, 81, 34, 253, 111, 64, 166, 19, 60, 98, 92, 40, 27, 166, 241, 171, 81, 171, 41, 87, 67, 235, 33, 176, 55, 217, 166, 182, 127, 48, 117, 28, 2, 17, 0, 0, 0, 8, 31, 144, 81, 122, 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