Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10d96fd0a83c9ac7b8e603cb71cc2b477cf8fe75a45f6e97a1c14834cdd91fe5

Tx prefix hash: 61481f0a2f8dcab83964a1b3fda1e2274cfc104771cea6389aa7d2b9c05568dc
Tx public key: 0ed3852ab9613c6f7a0bacdecdb31aa0b2a2a71076bb393d71323323c860e99c
Timestamp: 1638474935 Timestamp [UCT]: 2021-12-02 19:55:35 Age [y:d:h:m:s]: 03:163:00:12:53
Block: 387015 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 895237 RingCT/type: yes/0
Extra: 010ed3852ab9613c6f7a0bacdecdb31aa0b2a2a71076bb393d71323323c860e99c021100000003d6e4826b000000000000000000

1 output(s) for total of 32.037529411000 dcy

stealth address amount amount idx
00: d44c3db167bcfef94c643d4cd445c0dc83f5ce3264d2a16a50178d53f80e73c0 32.037529411000 780672 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": 387025, "vin": [ { "gen": { "height": 387015 } } ], "vout": [ { "amount": 32037529411, "target": { "key": "d44c3db167bcfef94c643d4cd445c0dc83f5ce3264d2a16a50178d53f80e73c0" } } ], "extra": [ 1, 14, 211, 133, 42, 185, 97, 60, 111, 122, 11, 172, 222, 205, 179, 26, 160, 178, 162, 167, 16, 118, 187, 57, 61, 113, 50, 51, 35, 200, 96, 233, 156, 2, 17, 0, 0, 0, 3, 214, 228, 130, 107, 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