Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc6276b77725a02e4dd6f1c34578e55b135ee5160dd515cd3c6dd9de9b771fb3

Tx prefix hash: 887240fa640976c88fb7eff8af7e7a226e72b94469134bfd7d811f32f4e66e35
Tx public key: f890834a667e252a028ab95c1b091d59e49dcbf4d253fc839e14103342601e14
Timestamp: 1715256412 Timestamp [UCT]: 2024-05-09 12:06:52 Age [y:d:h:m:s]: 01:007:00:05:41
Block: 1018241 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 265912 RingCT/type: yes/0
Extra: 01f890834a667e252a028ab95c1b091d59e49dcbf4d253fc839e14103342601e140211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68f98f4ecdb4d1acae22fdf0465bf9181ab15f6c3d9bc94f233d7d6f42ca1cf2 0.600000000000 1482030 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": 1018251, "vin": [ { "gen": { "height": 1018241 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68f98f4ecdb4d1acae22fdf0465bf9181ab15f6c3d9bc94f233d7d6f42ca1cf2" } } ], "extra": [ 1, 248, 144, 131, 74, 102, 126, 37, 42, 2, 138, 185, 92, 27, 9, 29, 89, 228, 157, 203, 244, 210, 83, 252, 131, 158, 20, 16, 51, 66, 96, 30, 20, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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