Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83c35c6cbabdac8966f2dd0b48be04cc3e3c0052796a2b8bccadcf8ab7d9c90a

Tx prefix hash: 2ef77bec0ef8f72488ca5b5747eb8a9d09f94a7b48edb7f9212cfc55c7a86248
Tx public key: 5345c7b581a8dd9907c8cf8b6bf788869765452251f823f7bdadb13f6f84f3d7
Timestamp: 1734079057 Timestamp [UCT]: 2024-12-13 08:37:37 Age [y:d:h:m:s]: 00:147:01:56:14
Block: 1174192 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104901 RingCT/type: yes/0
Extra: 015345c7b581a8dd9907c8cf8b6bf788869765452251f823f7bdadb13f6f84f3d7021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e90856680ef202dc0ad64dc0af94600e7deeefd2644c9536045feb92f864e1e 0.600000000000 1660311 of 15

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": 1174202, "vin": [ { "gen": { "height": 1174192 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e90856680ef202dc0ad64dc0af94600e7deeefd2644c9536045feb92f864e1e" } } ], "extra": [ 1, 83, 69, 199, 181, 129, 168, 221, 153, 7, 200, 207, 139, 107, 247, 136, 134, 151, 101, 69, 34, 81, 248, 35, 247, 189, 173, 177, 63, 111, 132, 243, 215, 2, 17, 0, 0, 0, 9, 0, 127, 151, 138, 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