Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0fe9e5339063cce02e1c3394af9e5e4485c670bb7ffaf04ddf8a274b91d68fc6

Tx prefix hash: 589977b362dce49acba851c1aef5c9ab4ddc5818a1c22cca918316c38644504d
Tx public key: 3b20f4d8c26bed20b654407e765c423c3366956577bfe7efe637c91d48bd7ca8
Timestamp: 1638008047 Timestamp [UCT]: 2021-11-27 10:14:07 Age [y:d:h:m:s]: 03:339:01:28:36
Block: 383185 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1018722 RingCT/type: yes/0
Extra: 013b20f4d8c26bed20b654407e765c423c3366956577bfe7efe637c91d48bd7ca8021100000009b494d89c000000000000000000

1 output(s) for total of 32.987500013000 dcy

stealth address amount amount idx
00: b3afafaf3a8ebab416af3efde62394f30c000f9a38c17ae7f1d1bedb35c0e2f9 32.987500013000 773662 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": 383195, "vin": [ { "gen": { "height": 383185 } } ], "vout": [ { "amount": 32987500013, "target": { "key": "b3afafaf3a8ebab416af3efde62394f30c000f9a38c17ae7f1d1bedb35c0e2f9" } } ], "extra": [ 1, 59, 32, 244, 216, 194, 107, 237, 32, 182, 84, 64, 126, 118, 92, 66, 60, 51, 102, 149, 101, 119, 191, 231, 239, 230, 55, 201, 29, 72, 189, 124, 168, 2, 17, 0, 0, 0, 9, 180, 148, 216, 156, 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