Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0bd128ead29cc1d3c7687c9ebc39db0c037e9f3cb9b0808b9122c06d0e605301

Tx prefix hash: 77332d9ae791b6e1f0eea35665740ae2add40e37e4252fe66205345a6a270639
Tx public key: 19ec8cd9b343ffbcb1436461cfc8bd238cc591e7271f550a01d5e4f1544c78dc
Timestamp: 1734704728 Timestamp [UCT]: 2024-12-20 14:25:28 Age [y:d:h:m:s]: 00:094:19:26:12
Block: 1179381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67511 RingCT/type: yes/0
Extra: 0119ec8cd9b343ffbcb1436461cfc8bd238cc591e7271f550a01d5e4f1544c78dc0211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d882bcff83830562447fbb89df63fb687fe13f8eb0420c6a1c3a19fe490b3c02 0.600000000000 1665776 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": 1179391, "vin": [ { "gen": { "height": 1179381 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d882bcff83830562447fbb89df63fb687fe13f8eb0420c6a1c3a19fe490b3c02" } } ], "extra": [ 1, 25, 236, 140, 217, 179, 67, 255, 188, 177, 67, 100, 97, 207, 200, 189, 35, 140, 197, 145, 231, 39, 31, 85, 10, 1, 213, 228, 241, 84, 76, 120, 220, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 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