Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a9a9bd9289dd9b55fb243bde471bc525dd5213baefe2c12a090059e8550d1db

Tx prefix hash: 99c2c93af3918499f5923038f13fa7de1fd9f381c0e515437fb1788c6eea282a
Tx public key: 2736d5d11ca3347235acc0694c7ca7217e9fe85cd6364f1af12532424c655a6b
Timestamp: 1719683403 Timestamp [UCT]: 2024-06-29 17:50:03 Age [y:d:h:m:s]: 00:337:16:06:36
Block: 1054924 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241338 RingCT/type: yes/0
Extra: 012736d5d11ca3347235acc0694c7ca7217e9fe85cd6364f1af12532424c655a6b02110000000c7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc3df949710865cb3f9801717363ce8e94d5e8a37b9f93cdf8acbe0189c06d5f 0.600000000000 1525315 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": 1054934, "vin": [ { "gen": { "height": 1054924 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc3df949710865cb3f9801717363ce8e94d5e8a37b9f93cdf8acbe0189c06d5f" } } ], "extra": [ 1, 39, 54, 213, 209, 28, 163, 52, 114, 53, 172, 192, 105, 76, 124, 167, 33, 126, 159, 232, 92, 214, 54, 79, 26, 241, 37, 50, 66, 76, 101, 90, 107, 2, 17, 0, 0, 0, 12, 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