Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dfab442790f62e4ded7a37343dc7f9566425d5565f6fcb2186378c9bfc2c6c7b

Tx prefix hash: 9db34657a288bed3dca70f411f761147f9bbbd8b31f3696536b26b7c8e2bb23b
Tx public key: 9884032198eff3020c51c4493058d8d52dcab4d2b40a06a9ed6ed2972ab7a32a
Timestamp: 1583540532 Timestamp [UCT]: 2020-03-07 00:22:12 Age [y:d:h:m:s]: 04:268:06:12:15
Block: 78018 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1086070 RingCT/type: yes/0
Extra: 019884032198eff3020c51c4493058d8d52dcab4d2b40a06a9ed6ed2972ab7a32a0211000000114ac5aa02000000000000000000

1 output(s) for total of 338.450197637000 dcy

stealth address amount amount idx
00: 370c183909eafc17040d9276ff29a1aa54933e70679df152efb6db36d18446a1 338.450197637000 143275 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": 78028, "vin": [ { "gen": { "height": 78018 } } ], "vout": [ { "amount": 338450197637, "target": { "key": "370c183909eafc17040d9276ff29a1aa54933e70679df152efb6db36d18446a1" } } ], "extra": [ 1, 152, 132, 3, 33, 152, 239, 243, 2, 12, 81, 196, 73, 48, 88, 216, 213, 45, 202, 180, 210, 180, 10, 6, 169, 237, 110, 210, 151, 42, 183, 163, 42, 2, 17, 0, 0, 0, 17, 74, 197, 170, 2, 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