Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44fcb0e64a78f5f222a51b5a7aebf7075ee5c9cb08327f9a1a438754df840956

Tx prefix hash: 55e3fc377c23cf5d12379a6955f56b3a3659a7259a93c3e57bf8707a0510ceef
Tx public key: 44e988ef64947288a6975fcbb1cd73a591e5dba85c5a904bd9f8a03662e84a13
Timestamp: 1698570359 Timestamp [UCT]: 2023-10-29 09:05:59 Age [y:d:h:m:s]: 01:163:07:54:38
Block: 880112 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 377719 RingCT/type: yes/0
Extra: 0144e988ef64947288a6975fcbb1cd73a591e5dba85c5a904bd9f8a03662e84a13021100000005faf35c9c000000000000000000

1 output(s) for total of 0.744429551000 dcy

stealth address amount amount idx
00: ae03671acf9cf50dd72201b3e6aa030f278acd0bf600e718dcc0fdf9bbac5865 0.744429551000 1335654 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": 880122, "vin": [ { "gen": { "height": 880112 } } ], "vout": [ { "amount": 744429551, "target": { "key": "ae03671acf9cf50dd72201b3e6aa030f278acd0bf600e718dcc0fdf9bbac5865" } } ], "extra": [ 1, 68, 233, 136, 239, 100, 148, 114, 136, 166, 151, 95, 203, 177, 205, 115, 165, 145, 229, 219, 168, 92, 90, 144, 75, 217, 248, 160, 54, 98, 232, 74, 19, 2, 17, 0, 0, 0, 5, 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