Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8794ac7bebb62b213891b95d761c671bc5d8a69c48b935c50fed9bbc6258e54

Tx prefix hash: 38908757d575d6ef1de6d96e0ca2e798df6a5e1d8291aabc59900511fb37576e
Tx public key: 9bf1a214f077042a85858c7be0c17c4ec3bce317e2c45f6c72c0db0fa87e5c72
Timestamp: 1657143098 Timestamp [UCT]: 2022-07-06 21:31:38 Age [y:d:h:m:s]: 02:271:00:36:27
Block: 538140 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 714831 RingCT/type: yes/0
Extra: 019bf1a214f077042a85858c7be0c17c4ec3bce317e2c45f6c72c0db0fa87e5c72021100000003faf35c9c000000000000000000

1 output(s) for total of 10.113906563000 dcy

stealth address amount amount idx
00: 5ff93e0e5e7f726eeb32a3303e94f1730be5191a546e3feec0460f41b6b489c1 10.113906563000 968103 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": 538150, "vin": [ { "gen": { "height": 538140 } } ], "vout": [ { "amount": 10113906563, "target": { "key": "5ff93e0e5e7f726eeb32a3303e94f1730be5191a546e3feec0460f41b6b489c1" } } ], "extra": [ 1, 155, 241, 162, 20, 240, 119, 4, 42, 133, 133, 140, 123, 224, 193, 124, 78, 195, 188, 227, 23, 226, 196, 95, 108, 114, 192, 219, 15, 168, 126, 92, 114, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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