Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5308c0ae531bd0b35f22c64c2f1bb0740bbfa792778a797955d5c34d05e7749a

Tx prefix hash: 50cbb9fb4b6bee6dcea35ec76e10f1f70ccef733598ac2a691ecc3cb592f627a
Tx public key: 4732d79737d0e9491f79d9b7fad5f7e7f00e957f123b9a10068a19c20d003ddb
Timestamp: 1698582324 Timestamp [UCT]: 2023-10-29 12:25:24 Age [y:d:h:m:s]: 01:144:23:34:36
Block: 880210 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364606 RingCT/type: yes/0
Extra: 014732d79737d0e9491f79d9b7fad5f7e7f00e957f123b9a10068a19c20d003ddb02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.743873161000 dcy

stealth address amount amount idx
00: e5a01479027cc8fb0d0aded7ce4bbed59bb6b08932d41dcd3d777e8682930602 0.743873161000 1335756 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": 880220, "vin": [ { "gen": { "height": 880210 } } ], "vout": [ { "amount": 743873161, "target": { "key": "e5a01479027cc8fb0d0aded7ce4bbed59bb6b08932d41dcd3d777e8682930602" } } ], "extra": [ 1, 71, 50, 215, 151, 55, 208, 233, 73, 31, 121, 217, 183, 250, 213, 247, 231, 240, 14, 149, 127, 18, 59, 154, 16, 6, 138, 25, 194, 13, 0, 61, 219, 2, 17, 0, 0, 0, 1, 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