Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d68d78a6c52f0337e8dc1ba56a28f8ba476ec578048cfc4758817f5f39abb87

Tx prefix hash: bb7f98549e73b72b8ffd6aa125d8a97d21e5cd014633ba9dcb1775cf0415bfce
Tx public key: de173f0b3afd9e5151dad00cbc9424002849e7c68eb2c742d4a6b9140bf0b422
Timestamp: 1725172930 Timestamp [UCT]: 2024-09-01 06:42:10 Age [y:d:h:m:s]: 00:217:20:21:56
Block: 1100441 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155529 RingCT/type: yes/0
Extra: 01de173f0b3afd9e5151dad00cbc9424002849e7c68eb2c742d4a6b9140bf0b42202110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da9a8278c6541b0a01aa10fb3cc1e520b84b304f041efe3f700d86a9a29490ef 0.600000000000 1576420 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": 1100451, "vin": [ { "gen": { "height": 1100441 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da9a8278c6541b0a01aa10fb3cc1e520b84b304f041efe3f700d86a9a29490ef" } } ], "extra": [ 1, 222, 23, 63, 11, 58, 253, 158, 81, 81, 218, 208, 12, 188, 148, 36, 0, 40, 73, 231, 198, 142, 178, 199, 66, 212, 166, 185, 20, 11, 240, 180, 34, 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