Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54698e6aab634a43918909938ee029085fad8fbc7f0bb264e5dbb78afdfed45e

Tx prefix hash: ad29d368cd78cd48f2b3d7b46b085ad4d71bd68dd754d5bb26adb91acfa900e7
Tx public key: c51c0395dcb6e0a923e8e75e49a2a0fc99cd047fedd80830a392d48f4cbb528b
Timestamp: 1727669167 Timestamp [UCT]: 2024-09-30 04:06:07 Age [y:d:h:m:s]: 00:210:11:07:12
Block: 1121140 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150240 RingCT/type: yes/0
Extra: 01c51c0395dcb6e0a923e8e75e49a2a0fc99cd047fedd80830a392d48f4cbb528b02110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7adcc6657aa6d23efb95373ee6b9439396652e986c5d5f6fba842c38f2bccee7 0.600000000000 1603303 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": 1121150, "vin": [ { "gen": { "height": 1121140 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7adcc6657aa6d23efb95373ee6b9439396652e986c5d5f6fba842c38f2bccee7" } } ], "extra": [ 1, 197, 28, 3, 149, 220, 182, 224, 169, 35, 232, 231, 94, 73, 162, 160, 252, 153, 205, 4, 127, 237, 216, 8, 48, 163, 146, 212, 143, 76, 187, 82, 139, 2, 17, 0, 0, 0, 8, 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