Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35630ac021c7e3ed7cb4d02f1af331d5abb94d12b1a47e978f375bd5647b6ff9

Tx prefix hash: 27b932b7c1734b7696c258af2737409bd3b0678914d6954453a7bc8dbf39b743
Tx public key: 9eab29bf31238a8f606cf44b3717a2efc535c7a93118c3ddab92b01830ab8faf
Timestamp: 1735751965 Timestamp [UCT]: 2025-01-01 17:19:25 Age [y:d:h:m:s]: 00:133:23:36:43
Block: 1188014 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95570 RingCT/type: yes/0
Extra: 019eab29bf31238a8f606cf44b3717a2efc535c7a93118c3ddab92b01830ab8faf0211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e69584684c59ff505c83c4021a20f17d638b71616c8dab8a05aa22f8c76af79 0.600000000000 1674513 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": 1188024, "vin": [ { "gen": { "height": 1188014 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e69584684c59ff505c83c4021a20f17d638b71616c8dab8a05aa22f8c76af79" } } ], "extra": [ 1, 158, 171, 41, 191, 49, 35, 138, 143, 96, 108, 244, 75, 55, 23, 162, 239, 197, 53, 199, 169, 49, 24, 195, 221, 171, 146, 176, 24, 48, 171, 143, 175, 2, 17, 0, 0, 0, 9, 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