Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8d89871a1cda7e40b83f0c38de3d8530d155fe9211ff34997fd30ad1f8a0792

Tx prefix hash: 76579a8c50648eb4b9ad635b0a9e7a0f5fd7cb377afeb7ffdea98b405cdcba9c
Tx public key: da10c456b7a887f2affe1fdfe83ffc8c0d5ae55d1018f97f96caef88c56a72ab
Timestamp: 1736245807 Timestamp [UCT]: 2025-01-07 10:30:07 Age [y:d:h:m:s]: 00:085:21:55:41
Block: 1192104 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 61180 RingCT/type: yes/0
Extra: 01da10c456b7a887f2affe1fdfe83ffc8c0d5ae55d1018f97f96caef88c56a72ab021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 12938cf67ce1cf4d847f2c32c5ac762ce22a5fc2a8631949bd23193b81e87605 0.600000000000 1678651 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": 1192114, "vin": [ { "gen": { "height": 1192104 } } ], "vout": [ { "amount": 600000000, "target": { "key": "12938cf67ce1cf4d847f2c32c5ac762ce22a5fc2a8631949bd23193b81e87605" } } ], "extra": [ 1, 218, 16, 196, 86, 183, 168, 135, 242, 175, 254, 31, 223, 232, 63, 252, 140, 13, 90, 229, 93, 16, 24, 249, 127, 150, 202, 239, 136, 197, 106, 114, 171, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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