Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 556a63a1659fd4d68570fd814a0bcbe871f6638a358dc9e8f11261de37f79778

Tx prefix hash: 56d4511b588b1c1066f9f5ffcefda713903934870640e64e7f5baebb560fc7e5
Tx public key: 4c35abe7efe68d24ef429a34870060b3fbf452017d2e282e6842c413dcc128f0
Timestamp: 1708194215 Timestamp [UCT]: 2024-02-17 18:23:35 Age [y:d:h:m:s]: 01:034:11:39:26
Block: 959676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285680 RingCT/type: yes/0
Extra: 014c35abe7efe68d24ef429a34870060b3fbf452017d2e282e6842c413dcc128f00211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 81a5cfb9d691e4e64f13d9ec6a07f78a7a39856d8be818da65eae697daa630fe 0.600000000000 1419229 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": 959686, "vin": [ { "gen": { "height": 959676 } } ], "vout": [ { "amount": 600000000, "target": { "key": "81a5cfb9d691e4e64f13d9ec6a07f78a7a39856d8be818da65eae697daa630fe" } } ], "extra": [ 1, 76, 53, 171, 231, 239, 230, 141, 36, 239, 66, 154, 52, 135, 0, 96, 179, 251, 244, 82, 1, 125, 46, 40, 46, 104, 66, 196, 19, 220, 193, 40, 240, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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