Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f87e5cf6160cd9dc06a8a49fa434c2b278b272b57582c1ed4a83a0131d3dccaa

Tx prefix hash: b267d5559947355b394cb60abace7e559d6a65ff2e83fcc9d39b5e4ffc9671bb
Tx public key: 03f5472ad67d1c05c3df834db9ff67cff9e09ae846fd7e113fb17a01c2185119
Timestamp: 1720501308 Timestamp [UCT]: 2024-07-09 05:01:48 Age [y:d:h:m:s]: 00:278:15:37:31
Block: 1061719 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199090 RingCT/type: yes/0
Extra: 0103f5472ad67d1c05c3df834db9ff67cff9e09ae846fd7e113fb17a01c218511902110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a9025266774cc2775dd0f158aa1408bc965c835c20054fd9d07b6c96027d1ae 0.600000000000 1532214 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": 1061729, "vin": [ { "gen": { "height": 1061719 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a9025266774cc2775dd0f158aa1408bc965c835c20054fd9d07b6c96027d1ae" } } ], "extra": [ 1, 3, 245, 71, 42, 214, 125, 28, 5, 195, 223, 131, 77, 185, 255, 103, 207, 249, 224, 154, 232, 70, 253, 126, 17, 63, 177, 122, 1, 194, 24, 81, 25, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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