Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd3a8fb49a08a0025d9630a4139be3ac3250a14a04b21b479ca3d2dcc8f0dc80

Tx prefix hash: 6b9bdb74c60e4d6644ae9bfd0924e69ef53a4902ba131e02c47eb58806c520f8
Tx public key: bdab7915109dc6848e3fc50650e97c832c541105b32be2e18cecdd86b87a3e60
Timestamp: 1722473519 Timestamp [UCT]: 2024-08-01 00:51:59 Age [y:d:h:m:s]: 00:242:19:44:23
Block: 1078059 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173447 RingCT/type: yes/0
Extra: 01bdab7915109dc6848e3fc50650e97c832c541105b32be2e18cecdd86b87a3e6002110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 30f7193ab56cc0dffaea85faf39d106dc86f6a74d728e3195665f39e5db8ee8c 0.600000000000 1550616 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": 1078069, "vin": [ { "gen": { "height": 1078059 } } ], "vout": [ { "amount": 600000000, "target": { "key": "30f7193ab56cc0dffaea85faf39d106dc86f6a74d728e3195665f39e5db8ee8c" } } ], "extra": [ 1, 189, 171, 121, 21, 16, 157, 198, 132, 142, 63, 197, 6, 80, 233, 124, 131, 44, 84, 17, 5, 179, 43, 226, 225, 140, 236, 221, 134, 184, 122, 62, 96, 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