Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82070ee7d93e7679ed7f6d35c7a18d0b1eb0b982739d89bd8094481531d3f37c

Tx prefix hash: 556f098a9d6769eccf7271cc3f2405e71ddf9079f4b33241f83448b9a82653f4
Tx public key: 20fab756020c886ffe0d753c98d2e15ff0d2336391a0d4444e4b5fd68831308f
Timestamp: 1736640352 Timestamp [UCT]: 2025-01-12 00:05:52 Age [y:d:h:m:s]: 01:020:16:38:06
Block: 1195367 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273088 RingCT/type: yes/0
Extra: 0120fab756020c886ffe0d753c98d2e15ff0d2336391a0d4444e4b5fd68831308f0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f57682d08cbc2b605cb7388be4ae127ab519448b0b798eea2f5a5c5d9a7a6fe 0.600000000000 1681956 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": 1195377, "vin": [ { "gen": { "height": 1195367 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f57682d08cbc2b605cb7388be4ae127ab519448b0b798eea2f5a5c5d9a7a6fe" } } ], "extra": [ 1, 32, 250, 183, 86, 2, 12, 136, 111, 254, 13, 117, 60, 152, 210, 225, 95, 240, 210, 51, 99, 145, 160, 212, 68, 78, 75, 95, 214, 136, 49, 48, 143, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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