Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd3fdecfcf5ba7878260f411045eb585d3f3d06ead156cf96b925c16f8e10c98

Tx prefix hash: 0ac241afc908f3ca1071864c6e1b98415615911ee63dc1fe83545d05e14a812c
Tx public key: 5c45f155a4d7352e5024e4d11613c43e32c3d6713ec5485fa8858a4b86e0559d
Timestamp: 1725665552 Timestamp [UCT]: 2024-09-06 23:32:32 Age [y:d:h:m:s]: 00:265:04:09:36
Block: 1104529 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189399 RingCT/type: yes/0
Extra: 015c45f155a4d7352e5024e4d11613c43e32c3d6713ec5485fa8858a4b86e0559d021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 973d25060a4d3b54ec17f1bf299265964ba2bea4b2ecf6a30bd4cdcf3317f380 0.600000000000 1581702 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": 1104539, "vin": [ { "gen": { "height": 1104529 } } ], "vout": [ { "amount": 600000000, "target": { "key": "973d25060a4d3b54ec17f1bf299265964ba2bea4b2ecf6a30bd4cdcf3317f380" } } ], "extra": [ 1, 92, 69, 241, 85, 164, 215, 53, 46, 80, 36, 228, 209, 22, 19, 196, 62, 50, 195, 214, 113, 62, 197, 72, 95, 168, 133, 138, 75, 134, 224, 85, 157, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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