Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 364b80478a1101f0b0bdfa643db37011130365d358c2fad8d25b3ff914c71ee1

Tx prefix hash: a78d66fa5525eb2a37311d4986bb0e941f359e090b0dcb5ffd2e639305022203
Tx public key: 686654e9db071af22fce2f05e803d5696c1667af167f80691e45485aa0705d99
Timestamp: 1697306320 Timestamp [UCT]: 2023-10-14 17:58:40 Age [y:d:h:m:s]: 01:097:06:29:00
Block: 869618 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330739 RingCT/type: yes/0
Extra: 01686654e9db071af22fce2f05e803d5696c1667af167f80691e45485aa0705d99021100000008faf35c9c000000000000000000

1 output(s) for total of 0.806481851000 dcy

stealth address amount amount idx
00: eb081ccdf3ec309eea64b84813de20693e14a665c2db2d9d014a63aef1dfe923 0.806481851000 1324467 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": 869628, "vin": [ { "gen": { "height": 869618 } } ], "vout": [ { "amount": 806481851, "target": { "key": "eb081ccdf3ec309eea64b84813de20693e14a665c2db2d9d014a63aef1dfe923" } } ], "extra": [ 1, 104, 102, 84, 233, 219, 7, 26, 242, 47, 206, 47, 5, 232, 3, 213, 105, 108, 22, 103, 175, 22, 127, 128, 105, 30, 69, 72, 90, 160, 112, 93, 153, 2, 17, 0, 0, 0, 8, 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