Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8cacdc58e3fe4e94e258a75464bc17b153141540a854cc1d73daad8617a32562

Tx prefix hash: 9bd9132a0dc72f57a2f69a95f55532544b692104076f1903bf6b6c0ea62c62fb
Tx public key: 045fa28ad031e7f8f38377533c83310cd50d93984bac93cb24cfcb22638418e8
Timestamp: 1694717620 Timestamp [UCT]: 2023-09-14 18:53:40 Age [y:d:h:m:s]: 01:204:09:53:40
Block: 848138 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 407189 RingCT/type: yes/0
Extra: 01045fa28ad031e7f8f38377533c83310cd50d93984bac93cb24cfcb22638418e80211000000164b8f5122000000000000000000

1 output(s) for total of 0.950094462000 dcy

stealth address amount amount idx
00: b40d4dbaa6a6319d1d2be59ef342d43b71d53e9e1e4eb6906c43d9d2048d8e9a 0.950094462000 1301722 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": 848148, "vin": [ { "gen": { "height": 848138 } } ], "vout": [ { "amount": 950094462, "target": { "key": "b40d4dbaa6a6319d1d2be59ef342d43b71d53e9e1e4eb6906c43d9d2048d8e9a" } } ], "extra": [ 1, 4, 95, 162, 138, 208, 49, 231, 248, 243, 131, 119, 83, 60, 131, 49, 12, 213, 13, 147, 152, 75, 172, 147, 203, 36, 207, 203, 34, 99, 132, 24, 232, 2, 17, 0, 0, 0, 22, 75, 143, 81, 34, 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