Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c7fc5b26311e85bf42f65daffbcf323f21837ac3bf00bfd900a5234be77bde8

Tx prefix hash: 314a1dc86e5720532e4b2caa902f6d1205c7da8672c1847f77ea36a2caaa0838
Tx public key: 69666a774997832cfa56e5b42eff24244cb6b822c068eb86b0c4124bd1accc95
Timestamp: 1710344260 Timestamp [UCT]: 2024-03-13 15:37:40 Age [y:d:h:m:s]: 00:315:12:25:50
Block: 977520 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225796 RingCT/type: yes/0
Extra: 0169666a774997832cfa56e5b42eff24244cb6b822c068eb86b0c4124bd1accc950211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4525b65f2b31080eddd537ca18f99b8f0cab2d28d79743c2fee68de6b324a531 0.600000000000 1437523 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": 977530, "vin": [ { "gen": { "height": 977520 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4525b65f2b31080eddd537ca18f99b8f0cab2d28d79743c2fee68de6b324a531" } } ], "extra": [ 1, 105, 102, 106, 119, 73, 151, 131, 44, 250, 86, 229, 180, 46, 255, 36, 36, 76, 182, 184, 34, 192, 104, 235, 134, 176, 196, 18, 75, 209, 172, 204, 149, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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