Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 886e1c477c280e7d6c5c6e36b23ff250f933f5882c7b30b4381d4add96cd25d2

Tx prefix hash: d63f6857340e863d573b996d2d5d3064db5d37119dbf1df1b96bd1790b6c9a29
Tx public key: 8dd1bcd36923d3b8e5607a8a1bfe71e7e7240da0abb33eadd9aa3ae0b2441541
Timestamp: 1682238435 Timestamp [UCT]: 2023-04-23 08:27:15 Age [y:d:h:m:s]: 01:261:22:55:35
Block: 744739 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 448703 RingCT/type: yes/0
Extra: 018dd1bcd36923d3b8e5607a8a1bfe71e7e7240da0abb33eadd9aa3ae0b244154102110000000db3164c24000000000000000000

1 output(s) for total of 2.091080480000 dcy

stealth address amount amount idx
00: b8771cb89f1a23622f7ee2a8b814ce5074265b5aeb8cdc872b1092066f523817 2.091080480000 1192114 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": 744749, "vin": [ { "gen": { "height": 744739 } } ], "vout": [ { "amount": 2091080480, "target": { "key": "b8771cb89f1a23622f7ee2a8b814ce5074265b5aeb8cdc872b1092066f523817" } } ], "extra": [ 1, 141, 209, 188, 211, 105, 35, 211, 184, 229, 96, 122, 138, 27, 254, 113, 231, 231, 36, 13, 160, 171, 179, 62, 173, 217, 170, 58, 224, 178, 68, 21, 65, 2, 17, 0, 0, 0, 13, 179, 22, 76, 36, 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