Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 967f3649c482874a802e355562691e68f3bc51864a99d739494fa2d866dc2ca7

Tx prefix hash: f9d6be0a26dbd0956227648a1c3a7f2332c45e12661043e64d1a1df90e12e722
Tx public key: 517e45b848eec2bce44c4f4f5b892605b0db23efded8eb54878627ca6df81536
Timestamp: 1701130303 Timestamp [UCT]: 2023-11-28 00:11:43 Age [y:d:h:m:s]: 01:360:00:27:47
Block: 901123 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 516187 RingCT/type: yes/0
Extra: 01517e45b848eec2bce44c4f4f5b892605b0db23efded8eb54878627ca6df8153602110000000875e3f0e9000000000000000000

1 output(s) for total of 0.634169584000 dcy

stealth address amount amount idx
00: 6d791f6f9a439822f834b198c2cd365695f8807335afbb6de1eef664b64f9dad 0.634169584000 1357654 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": 901133, "vin": [ { "gen": { "height": 901123 } } ], "vout": [ { "amount": 634169584, "target": { "key": "6d791f6f9a439822f834b198c2cd365695f8807335afbb6de1eef664b64f9dad" } } ], "extra": [ 1, 81, 126, 69, 184, 72, 238, 194, 188, 228, 76, 79, 79, 91, 137, 38, 5, 176, 219, 35, 239, 222, 216, 235, 84, 135, 134, 39, 202, 109, 248, 21, 54, 2, 17, 0, 0, 0, 8, 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