Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 398ed0f145e16fe0f10165d8d2c0e87dc13bb65534f639179b96ab13193c39fb

Tx prefix hash: b29a77c51f36cb0fda81dbf8007bba123eaa4b9fa856cac5ec8bcecdc5d0725e
Tx public key: 4c55db2bf16bd5422e796dde50e53c4d96d98d9dac04777237c1495c57621606
Timestamp: 1626164307 Timestamp [UCT]: 2021-07-13 08:18:27 Age [y:d:h:m:s]: 03:277:16:23:19
Block: 293007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 969348 RingCT/type: yes/0
Extra: 014c55db2bf16bd5422e796dde50e53c4d96d98d9dac04777237c1495c5762160602110000000145e5d62d000000000000000000

1 output(s) for total of 65.636690740000 dcy

stealth address amount amount idx
00: 27fc4cbef42ca99aab2e54f4d16b64734384018dc93bd8cda8e66cd1ca4668af 65.636690740000 613925 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": 293017, "vin": [ { "gen": { "height": 293007 } } ], "vout": [ { "amount": 65636690740, "target": { "key": "27fc4cbef42ca99aab2e54f4d16b64734384018dc93bd8cda8e66cd1ca4668af" } } ], "extra": [ 1, 76, 85, 219, 43, 241, 107, 213, 66, 46, 121, 109, 222, 80, 229, 60, 77, 150, 217, 141, 157, 172, 4, 119, 114, 55, 193, 73, 92, 87, 98, 22, 6, 2, 17, 0, 0, 0, 1, 69, 229, 214, 45, 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