Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 672719db4868e817849c57a17ead8ff151330dd4056756942dc9ea78aedd728d

Tx prefix hash: 20545ca7fec98ea9e57f38dcef4c87a1e7a59217889ec4b09428af00f2dad45e
Tx public key: ddd3911a946e8e9b02c035def16d345168d0aa049fcb905e2e8ba08559e92c97
Timestamp: 1707539618 Timestamp [UCT]: 2024-02-10 04:33:38 Age [y:d:h:m:s]: 00:273:19:20:08
Block: 954241 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196055 RingCT/type: yes/0
Extra: 01ddd3911a946e8e9b02c035def16d345168d0aa049fcb905e2e8ba08559e92c970211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e21fc45e1516d8e5d7d86f78499e9f3bae5ed215199b4a1960b16a53439e06fd 0.600000000000 1413517 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": 954251, "vin": [ { "gen": { "height": 954241 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e21fc45e1516d8e5d7d86f78499e9f3bae5ed215199b4a1960b16a53439e06fd" } } ], "extra": [ 1, 221, 211, 145, 26, 148, 110, 142, 155, 2, 192, 53, 222, 241, 109, 52, 81, 104, 208, 170, 4, 159, 203, 144, 94, 46, 139, 160, 133, 89, 233, 44, 151, 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