Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6d1e3e13f11bc887d8d1893cb269b07cc8aac90f4958b5b1c025b76cc547bfb

Tx prefix hash: a4e2e7347a022a99d9a89dd6fee08bec3f7e56fdcb465cffb0b993382bf6d7ff
Tx public key: 612ffd745146a998654365b2052a506ad68de8d24a5f80b4f20574b791784cfb
Timestamp: 1711055092 Timestamp [UCT]: 2024-03-21 21:04:52 Age [y:d:h:m:s]: 00:363:01:00:59
Block: 983419 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259576 RingCT/type: yes/0
Extra: 01612ffd745146a998654365b2052a506ad68de8d24a5f80b4f20574b791784cfb021100000001a5df9d86000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b677439459e375be3b0eb0156fa1452f9ee84a2cda34357581d7459fe00a24c1 0.600000000000 1443550 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": 983429, "vin": [ { "gen": { "height": 983419 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b677439459e375be3b0eb0156fa1452f9ee84a2cda34357581d7459fe00a24c1" } } ], "extra": [ 1, 97, 47, 253, 116, 81, 70, 169, 152, 101, 67, 101, 178, 5, 42, 80, 106, 214, 141, 232, 210, 74, 95, 128, 180, 242, 5, 116, 183, 145, 120, 76, 251, 2, 17, 0, 0, 0, 1, 165, 223, 157, 134, 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