Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44921bfb9164e6877fc83b9babc30d21d0fa08fddd3e22b0bf197f067eab5987

Tx prefix hash: 765e8f82fe0803191b0f38a6a0c4ba4631a6fbe147ababd66c467f5f0f73e98f
Tx public key: 91fee6abfabf8cf532f01f273a02e820d174bf60a5e4c9b665d9769bda4c4039
Timestamp: 1700211003 Timestamp [UCT]: 2023-11-17 08:50:03 Age [y:d:h:m:s]: 00:349:15:51:29
Block: 893498 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250385 RingCT/type: yes/0
Extra: 0191fee6abfabf8cf532f01f273a02e820d174bf60a5e4c9b665d9769bda4c403902110000000833af99f4000000000000000000

1 output(s) for total of 0.672156202000 dcy

stealth address amount amount idx
00: cd63575a2f8d7e0619216d5b73e8a87109dcf21ea8463f5ec1feaa721d2f2a27 0.672156202000 1349665 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": 893508, "vin": [ { "gen": { "height": 893498 } } ], "vout": [ { "amount": 672156202, "target": { "key": "cd63575a2f8d7e0619216d5b73e8a87109dcf21ea8463f5ec1feaa721d2f2a27" } } ], "extra": [ 1, 145, 254, 230, 171, 250, 191, 140, 245, 50, 240, 31, 39, 58, 2, 232, 32, 209, 116, 191, 96, 165, 228, 201, 182, 101, 217, 118, 155, 218, 76, 64, 57, 2, 17, 0, 0, 0, 8, 51, 175, 153, 244, 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