Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b87085b25894f8c8f205b601b848422ce6bc8622aa11dfbf3d770fdbaef5c7ee

Tx prefix hash: 9377eb615045dc633d1566a41129eaec64b9fdbea8d2e5fb3b481330448af413
Tx public key: ac73626d7ff17619d84f6c229f1a3f2e042d35a5fb6f9eed3962ff0f3e2869fd
Timestamp: 1732728665 Timestamp [UCT]: 2024-11-27 17:31:05 Age [y:d:h:m:s]: 00:106:23:41:26
Block: 1162984 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76281 RingCT/type: yes/0
Extra: 01ac73626d7ff17619d84f6c229f1a3f2e042d35a5fb6f9eed3962ff0f3e2869fd021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d8b26e5cca83536116027a3544d6671449ab7c01e23fa4b68773d714de8062e 0.600000000000 1648647 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": 1162994, "vin": [ { "gen": { "height": 1162984 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d8b26e5cca83536116027a3544d6671449ab7c01e23fa4b68773d714de8062e" } } ], "extra": [ 1, 172, 115, 98, 109, 127, 241, 118, 25, 216, 79, 108, 34, 159, 26, 63, 46, 4, 45, 53, 165, 251, 111, 158, 237, 57, 98, 255, 15, 62, 40, 105, 253, 2, 17, 0, 0, 0, 2, 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