Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82cfe8c0eccfdc0851a3d43c99f22d91441bf32f6b3496b16fcfd2ba094b614a

Tx prefix hash: fdd5c8927a47f07ebe3e6a2f13cf08dec19f80ff8164d75d260dce644f58de96
Tx public key: 79a6be0a9185d77d16aa84caafaee83442532f6b2468ee32c2c5c0501cbd40ec
Timestamp: 1722582403 Timestamp [UCT]: 2024-08-02 07:06:43 Age [y:d:h:m:s]: 00:247:02:19:10
Block: 1078964 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176496 RingCT/type: yes/0
Extra: 0179a6be0a9185d77d16aa84caafaee83442532f6b2468ee32c2c5c0501cbd40ec021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0dc4da204b192b83c4c4285641ebfff61e037dbd54e74ac8abbc50ea7102d137 0.600000000000 1551715 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": 1078974, "vin": [ { "gen": { "height": 1078964 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0dc4da204b192b83c4c4285641ebfff61e037dbd54e74ac8abbc50ea7102d137" } } ], "extra": [ 1, 121, 166, 190, 10, 145, 133, 215, 125, 22, 170, 132, 202, 175, 174, 232, 52, 66, 83, 47, 107, 36, 104, 238, 50, 194, 197, 192, 80, 28, 189, 64, 236, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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