Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4cf069614502dd00f5588b477be61729ce31664c1e935e8a04468743207ab6e4

Tx prefix hash: b13fb7048c96363725c5686ffd0b1eab672a895c553b1cec3a7f11ddb23eae86
Tx public key: 536ea4e469ee4bcd1d9595d018bbc4310b75cd632a9b90132f25da6ebed07b28
Timestamp: 1669351849 Timestamp [UCT]: 2022-11-25 04:50:49 Age [y:d:h:m:s]: 02:052:16:11:49
Block: 638552 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 559580 RingCT/type: yes/0
Extra: 01536ea4e469ee4bcd1d9595d018bbc4310b75cd632a9b90132f25da6ebed07b2802110000000a75e3f0e9000000000000000000

1 output(s) for total of 4.701237068000 dcy

stealth address amount amount idx
00: 2043c0fd7b097ea5a88d504984a631fac594d602b9c0cd6dbac3277112201c0a 4.701237068000 1078169 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": 638562, "vin": [ { "gen": { "height": 638552 } } ], "vout": [ { "amount": 4701237068, "target": { "key": "2043c0fd7b097ea5a88d504984a631fac594d602b9c0cd6dbac3277112201c0a" } } ], "extra": [ 1, 83, 110, 164, 228, 105, 238, 75, 205, 29, 149, 149, 208, 24, 187, 196, 49, 11, 117, 205, 99, 42, 155, 144, 19, 47, 37, 218, 110, 190, 208, 123, 40, 2, 17, 0, 0, 0, 10, 117, 227, 240, 233, 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