Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e30f957b9fd94a75a0341b6b76a5c48fa56d1854353ab14d2cbb72a9d626faea

Tx prefix hash: 7c325c79f7597fa277672c22c83fd4724ddae1bcad62eb0fde5735ba599cd86b
Tx public key: 781bb56d8949d87540cc2fe481b83733e3418cc249a48e47cea2790d1dfd3a0e
Timestamp: 1725996639 Timestamp [UCT]: 2024-09-10 19:30:39 Age [y:d:h:m:s]: 00:079:00:44:48
Block: 1107269 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 56513 RingCT/type: yes/0
Extra: 01781bb56d8949d87540cc2fe481b83733e3418cc249a48e47cea2790d1dfd3a0e02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 202a8380870fe2a113dfbce2ca5079c035c36b81d74e69a423d89461a3c1fa61 0.600000000000 1584880 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": 1107279, "vin": [ { "gen": { "height": 1107269 } } ], "vout": [ { "amount": 600000000, "target": { "key": "202a8380870fe2a113dfbce2ca5079c035c36b81d74e69a423d89461a3c1fa61" } } ], "extra": [ 1, 120, 27, 181, 109, 137, 73, 216, 117, 64, 204, 47, 228, 129, 184, 55, 51, 227, 65, 140, 194, 73, 164, 142, 71, 206, 162, 121, 13, 29, 253, 58, 14, 2, 17, 0, 0, 0, 7, 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