Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0634be4a7e1c386200e65b7d5f9bad64e8cef68100be14f1ac60d3c40922d2d4

Tx prefix hash: ad3c397c00a8637c8ee8295442fac611639f4e165d3decfe9c853225a96e0aa2
Tx public key: e8e93486cefc2fa23ad28f44cc98840bf8f1dd057fc6f44132bc1c32646caf6d
Timestamp: 1707770282 Timestamp [UCT]: 2024-02-12 20:38:02 Age [y:d:h:m:s]: 01:055:09:06:53
Block: 956157 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300610 RingCT/type: yes/0
Extra: 01e8e93486cefc2fa23ad28f44cc98840bf8f1dd057fc6f44132bc1c32646caf6d02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b75df8cd4fb9eec1368eb02bf599fbe4a48cea3c757a86a35a6ea58035356d2 0.600000000000 1415459 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": 956167, "vin": [ { "gen": { "height": 956157 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b75df8cd4fb9eec1368eb02bf599fbe4a48cea3c757a86a35a6ea58035356d2" } } ], "extra": [ 1, 232, 233, 52, 134, 206, 252, 47, 162, 58, 210, 143, 68, 204, 152, 132, 11, 248, 241, 221, 5, 127, 198, 244, 65, 50, 188, 28, 50, 100, 108, 175, 109, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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