Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0640883669b399331893db6c77b8c885dd4a035ba1147e2aebce2dfa191b8a26

Tx prefix hash: 3bf765270229e29880ec287a0a6ff463fe3b2adb332b495a667f795e16216fd7
Tx public key: c1afb3e1689240d473d817a6be5a6567250d081db2245e3004f32bf0ee32aae8
Timestamp: 1726458657 Timestamp [UCT]: 2024-09-16 03:50:57 Age [y:d:h:m:s]: 00:183:14:00:51
Block: 1111101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 131041 RingCT/type: yes/0
Extra: 01c1afb3e1689240d473d817a6be5a6567250d081db2245e3004f32bf0ee32aae8021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c6b587c6ca66675bb6c2a3f47118bc7e03c5442a90276ca3f2e0d39e279fb88 0.600000000000 1589944 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": 1111111, "vin": [ { "gen": { "height": 1111101 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c6b587c6ca66675bb6c2a3f47118bc7e03c5442a90276ca3f2e0d39e279fb88" } } ], "extra": [ 1, 193, 175, 179, 225, 104, 146, 64, 212, 115, 216, 23, 166, 190, 90, 101, 103, 37, 13, 8, 29, 178, 36, 94, 48, 4, 243, 43, 240, 238, 50, 170, 232, 2, 17, 0, 0, 0, 3, 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