Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3f4e3bac3bfb52adbc9d19403f3694db0ea6f6eeacd9cdcecb71d059d5a523d

Tx prefix hash: 62ea4f0bf87ab56cd4dea7b360522d395d5ca80ab47c72f87470fcdd4a2f5b1e
Tx public key: 447b04b76358e8bcefa16c4468bc8118a5ed923345e485f2c2d8db4ec4c30b04
Timestamp: 1699190092 Timestamp [UCT]: 2023-11-05 13:14:52 Age [y:d:h:m:s]: 01:176:07:07:51
Block: 885050 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 387200 RingCT/type: yes/0
Extra: 01447b04b76358e8bcefa16c4468bc8118a5ed923345e485f2c2d8db4ec4c30b0402110000000233af99f4000000000000000000

1 output(s) for total of 0.716905568000 dcy

stealth address amount amount idx
00: 257c148a8f30198021f8251a4dcaa0e2d9f8b58f27068b7aa44536a5b7c2932a 0.716905568000 1340803 of 0

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": 885060, "vin": [ { "gen": { "height": 885050 } } ], "vout": [ { "amount": 716905568, "target": { "key": "257c148a8f30198021f8251a4dcaa0e2d9f8b58f27068b7aa44536a5b7c2932a" } } ], "extra": [ 1, 68, 123, 4, 183, 99, 88, 232, 188, 239, 161, 108, 68, 104, 188, 129, 24, 165, 237, 146, 51, 69, 228, 133, 242, 194, 216, 219, 78, 196, 195, 11, 4, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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