Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55242ef6a9052e6bf7c4cb6128b027b37c9fbfb6244609b3ba86dd9c32aedfe6

Tx prefix hash: 22e0550bf0078262af3f76497760ecaf55bd907df35be05b121da2f8c3bf5315
Tx public key: b55096934449c97062aa8f690a275bf066a879316c8f3a4c7c7112312a3dcb87
Timestamp: 1732599146 Timestamp [UCT]: 2024-11-26 05:32:26 Age [y:d:h:m:s]: 00:359:02:29:03
Block: 1161911 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254196 RingCT/type: yes/0
Extra: 01b55096934449c97062aa8f690a275bf066a879316c8f3a4c7c7112312a3dcb870211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fae91264f7326ce8aa483c8e503d0b7de9bd5f67f2ecad4f8f9d399586d85ffe 0.600000000000 1647566 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": 1161921, "vin": [ { "gen": { "height": 1161911 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fae91264f7326ce8aa483c8e503d0b7de9bd5f67f2ecad4f8f9d399586d85ffe" } } ], "extra": [ 1, 181, 80, 150, 147, 68, 73, 201, 112, 98, 170, 143, 105, 10, 39, 91, 240, 102, 168, 121, 49, 108, 143, 58, 76, 124, 113, 18, 49, 42, 61, 203, 135, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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