Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28652a7224b20fa59760825e34f7cb122db2f6f4006b9a266af1ee62318a7c5e

Tx prefix hash: bee8b9ae433fd0b3bcdacc089a15276414d3350d92a5b1b7241a2fa5df156dfc
Tx public key: 8275e88be7e8b6f267de565d559f35b94c53b1e56b87ff77449126eeefc4e7bc
Timestamp: 1725175852 Timestamp [UCT]: 2024-09-01 07:30:52 Age [y:d:h:m:s]: 00:052:04:54:50
Block: 1100468 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37361 RingCT/type: yes/0
Extra: 018275e88be7e8b6f267de565d559f35b94c53b1e56b87ff77449126eeefc4e7bc02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb73b12c7fd0e507b1127fae0132fb88493424574258e4fb3821ae0076d948a4 0.600000000000 1576447 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": 1100478, "vin": [ { "gen": { "height": 1100468 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb73b12c7fd0e507b1127fae0132fb88493424574258e4fb3821ae0076d948a4" } } ], "extra": [ 1, 130, 117, 232, 139, 231, 232, 182, 242, 103, 222, 86, 93, 85, 159, 53, 185, 76, 83, 177, 229, 107, 135, 255, 119, 68, 145, 38, 238, 239, 196, 231, 188, 2, 17, 0, 0, 0, 2, 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