Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe49f502d552d3abe995b695895ba071853a73691e66c5066092e654f34cd73a

Tx prefix hash: a60dcc6b330f8b493ced46a28ad20b31c2217457eca012b7876bd6610b88d281
Tx public key: 773eaa7dfa423e7a0b9da3e95c0e6f68922a045d9cdc3cdae511c6c4943a0e56
Timestamp: 1688214223 Timestamp [UCT]: 2023-07-01 12:23:43 Age [y:d:h:m:s]: 01:194:04:11:28
Block: 794297 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 400126 RingCT/type: yes/0
Extra: 01773eaa7dfa423e7a0b9da3e95c0e6f68922a045d9cdc3cdae511c6c4943a0e560211000000044b8f5122000000000000000000

1 output(s) for total of 1.432730311000 dcy

stealth address amount amount idx
00: f0152a239c0f0e1468c572506c2e69af4e32643cbb6427cee8d43a5f736d9624 1.432730311000 1245032 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": 794307, "vin": [ { "gen": { "height": 794297 } } ], "vout": [ { "amount": 1432730311, "target": { "key": "f0152a239c0f0e1468c572506c2e69af4e32643cbb6427cee8d43a5f736d9624" } } ], "extra": [ 1, 119, 62, 170, 125, 250, 66, 62, 122, 11, 157, 163, 233, 92, 14, 111, 104, 146, 42, 4, 93, 156, 220, 60, 218, 229, 17, 198, 196, 148, 58, 14, 86, 2, 17, 0, 0, 0, 4, 75, 143, 81, 34, 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