Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f6fcf3740f58d9e459b0a7ae2a1a4b646ffce63c6d2a4ac185cc0266faeb452

Tx prefix hash: 06f71c0b4433681b2155198b8d8015a19e57aaa98d21cde7b6f46ed4cea8b00c
Tx public key: 0f0d5112712a569f293411b8a808de40152e90f52ba60de3269a3c05eab15e8d
Timestamp: 1679535997 Timestamp [UCT]: 2023-03-23 01:46:37 Age [y:d:h:m:s]: 02:063:21:45:51
Block: 722987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 567241 RingCT/type: yes/0
Extra: 010f0d5112712a569f293411b8a808de40152e90f52ba60de3269a3c05eab15e8d0211000000015029cbac000000000000000000

1 output(s) for total of 2.468560767000 dcy

stealth address amount amount idx
00: 6d3beca11ff55904d9f5dc8a227f676572b407f98cb5d2e9024bcd7a7749e875 2.468560767000 1167946 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": 722997, "vin": [ { "gen": { "height": 722987 } } ], "vout": [ { "amount": 2468560767, "target": { "key": "6d3beca11ff55904d9f5dc8a227f676572b407f98cb5d2e9024bcd7a7749e875" } } ], "extra": [ 1, 15, 13, 81, 18, 113, 42, 86, 159, 41, 52, 17, 184, 168, 8, 222, 64, 21, 46, 144, 245, 43, 166, 13, 227, 38, 154, 60, 5, 234, 177, 94, 141, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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