Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4262fe7833934724bb4576981b8d8102dbe58453e41e1bab1551694caa0f2010

Tx prefix hash: a85a096ec8d058fb0fb0cfc8d74f9e84825bf209d1dcec0830ec325db9497e7a
Tx public key: 5d3692d6ba71d39331329b6d5529dd34caebc0ed2940603abc758acedd577b04
Timestamp: 1633198076 Timestamp [UCT]: 2021-10-02 18:07:56 Age [y:d:h:m:s]: 03:036:22:33:27
Block: 345330 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 803314 RingCT/type: yes/0
Extra: 015d3692d6ba71d39331329b6d5529dd34caebc0ed2940603abc758acedd577b04021100000009f60c5d7e000000000000000000

1 output(s) for total of 44.033051832000 dcy

stealth address amount amount idx
00: 654c9b263549ec8bcc2e45f2a57cea15c1d24a4ea22bd4a62c8fb677df7690b7 44.033051832000 708446 of 0

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": 345340, "vin": [ { "gen": { "height": 345330 } } ], "vout": [ { "amount": 44033051832, "target": { "key": "654c9b263549ec8bcc2e45f2a57cea15c1d24a4ea22bd4a62c8fb677df7690b7" } } ], "extra": [ 1, 93, 54, 146, 214, 186, 113, 211, 147, 49, 50, 155, 109, 85, 41, 221, 52, 202, 235, 192, 237, 41, 64, 96, 58, 188, 117, 138, 206, 221, 87, 123, 4, 2, 17, 0, 0, 0, 9, 246, 12, 93, 126, 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