Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77281cc9f97ecaa3b3a90e2ed57da638c1412e3f4f2d36f74e13c99d2717360d

Tx prefix hash: c343181a913ead01ac9399e0d59750c0845c2aa9b0dd6f14ead8b9a2e9b6d114
Tx public key: 452779c18cd15336a0329dff26edcf3606677cb9413a972b0b1404d1f90588ff
Timestamp: 1685002214 Timestamp [UCT]: 2023-05-25 08:10:14 Age [y:d:h:m:s]: 02:167:19:00:47
Block: 767668 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 639705 RingCT/type: yes/0
Extra: 01452779c18cd15336a0329dff26edcf3606677cb9413a972b0b1404d1f90588ff0211000000037e406890000000000000000000

1 output(s) for total of 1.755486197000 dcy

stealth address amount amount idx
00: 03c818c335d68493516a6b0aff595d4e5cc65d3f47504bd62193f2b6919d241d 1.755486197000 1216801 of 0

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": 767678, "vin": [ { "gen": { "height": 767668 } } ], "vout": [ { "amount": 1755486197, "target": { "key": "03c818c335d68493516a6b0aff595d4e5cc65d3f47504bd62193f2b6919d241d" } } ], "extra": [ 1, 69, 39, 121, 193, 140, 209, 83, 54, 160, 50, 157, 255, 38, 237, 207, 54, 6, 103, 124, 185, 65, 58, 151, 43, 11, 20, 4, 209, 249, 5, 136, 255, 2, 17, 0, 0, 0, 3, 126, 64, 104, 144, 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