Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6bf76393ce6f3f289b4c11d074a8d26a77d8ba621f55731a673e31d454a3ace8

Tx prefix hash: 8260b58842c5eae4134aff1a7d7579d2f9965456f189817ae70c315853b5d459
Tx public key: e4dfa0a459acd29af74ee9baee111e4a1b0fb04073c9270eaecdbd0526a604ad
Timestamp: 1734535598 Timestamp [UCT]: 2024-12-18 15:26:38 Age [y:d:h:m:s]: 00:105:00:53:48
Block: 1177975 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74834 RingCT/type: yes/0
Extra: 01e4dfa0a459acd29af74ee9baee111e4a1b0fb04073c9270eaecdbd0526a604ad021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b282c376715c46d27b9eee905d89b78d2322638356e64f062e0751e72524eeb3 0.600000000000 1664356 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": 1177985, "vin": [ { "gen": { "height": 1177975 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b282c376715c46d27b9eee905d89b78d2322638356e64f062e0751e72524eeb3" } } ], "extra": [ 1, 228, 223, 160, 164, 89, 172, 210, 154, 247, 78, 233, 186, 238, 17, 30, 74, 27, 15, 176, 64, 115, 201, 39, 14, 174, 205, 189, 5, 38, 166, 4, 173, 2, 17, 0, 0, 0, 4, 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