Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b894d974be40e28dfacbdb53a09252469d667bb1debc578256e8714012f4f4bb

Tx prefix hash: ff660ce8067c018b2be6db5bf8141b2f004d15f11c9d5175f8c63422122d93b8
Tx public key: a5202d48984b5181083256cb7530c350135eae27a0c56394caed2814f34d7e7f
Timestamp: 1697231851 Timestamp [UCT]: 2023-10-13 21:17:31 Age [y:d:h:m:s]: 01:033:07:09:46
Block: 868997 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285003 RingCT/type: yes/0
Extra: 01a5202d48984b5181083256cb7530c350135eae27a0c56394caed2814f34d7e7f021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.810311924000 dcy

stealth address amount amount idx
00: f218970b45b0fa2f851ea4defc5e2eb13b43aabedd5c06937186e69d4f6de706 0.810311924000 1323824 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": 869007, "vin": [ { "gen": { "height": 868997 } } ], "vout": [ { "amount": 810311924, "target": { "key": "f218970b45b0fa2f851ea4defc5e2eb13b43aabedd5c06937186e69d4f6de706" } } ], "extra": [ 1, 165, 32, 45, 72, 152, 75, 81, 129, 8, 50, 86, 203, 117, 48, 195, 80, 19, 94, 174, 39, 160, 197, 99, 148, 202, 237, 40, 20, 243, 77, 126, 127, 2, 17, 0, 0, 0, 3, 230, 210, 127, 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