Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f895861755a3ccec6784794d668250940b02fa56a059f86c22a7dbbe22b85e35

Tx prefix hash: f7eb8e47ac07cfc243bbe57a4143a064df4734bf7444289631becb6ba07fcf76
Tx public key: c356803eacf68af7656aa9e027845fbff8d49e0640be4dcd69d300c42cb49fd2
Timestamp: 1688885135 Timestamp [UCT]: 2023-07-09 06:45:35 Age [y:d:h:m:s]: 01:130:01:32:59
Block: 799858 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354262 RingCT/type: yes/0
Extra: 01c356803eacf68af7656aa9e027845fbff8d49e0640be4dcd69d300c42cb49fd2021100000005faf35c9c000000000000000000

1 output(s) for total of 1.373215002000 dcy

stealth address amount amount idx
00: 4d1bd71c16ae086c8d1206cacb580ffa17290a15bb575c0b1f617d773ff3b715 1.373215002000 1250891 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": 799868, "vin": [ { "gen": { "height": 799858 } } ], "vout": [ { "amount": 1373215002, "target": { "key": "4d1bd71c16ae086c8d1206cacb580ffa17290a15bb575c0b1f617d773ff3b715" } } ], "extra": [ 1, 195, 86, 128, 62, 172, 246, 138, 247, 101, 106, 169, 224, 39, 132, 95, 191, 248, 212, 158, 6, 64, 190, 77, 205, 105, 211, 0, 196, 44, 180, 159, 210, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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