Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f865a7162e0b0f2b642f3297c87a6762f34de1a8a5876bf51376ffbf7ec32cc

Tx prefix hash: a72c49efca6365887e6c76897406026a3757858c78df8612a540acb9182c5ac7
Tx public key: 95d23ed778e5d70858497c9c75573307fa131e18b47d6586a9f38c30b66c5f3c
Timestamp: 1699090136 Timestamp [UCT]: 2023-11-04 09:28:56 Age [y:d:h:m:s]: 01:154:19:09:03
Block: 884409 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371613 RingCT/type: yes/0
Extra: 0195d23ed778e5d70858497c9c75573307fa131e18b47d6586a9f38c30b66c5f3c021100000009faf35c9c000000000000000000

1 output(s) for total of 0.720420154000 dcy

stealth address amount amount idx
00: 52a9fdb4f755b5f4e156e90633ee712861f769cf3e8f0f4d69e18baffc81d828 0.720420154000 1340148 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": 884419, "vin": [ { "gen": { "height": 884409 } } ], "vout": [ { "amount": 720420154, "target": { "key": "52a9fdb4f755b5f4e156e90633ee712861f769cf3e8f0f4d69e18baffc81d828" } } ], "extra": [ 1, 149, 210, 62, 215, 120, 229, 215, 8, 88, 73, 124, 156, 117, 87, 51, 7, 250, 19, 30, 24, 180, 125, 101, 134, 169, 243, 140, 48, 182, 108, 95, 60, 2, 17, 0, 0, 0, 9, 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