Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dedce85657c937173a774e7327616663a45e11ad488abafa528acabe9d21218a

Tx prefix hash: be5b864ae9f374c7f4a91c01363bf40a1e6df4ba64e45b9e92f46b218296f590
Tx public key: 1a128dcc29c0ce6bc99f49ec5e1503dc4d82ddb4ab8e1e7594863ff7c60da00c
Timestamp: 1681365131 Timestamp [UCT]: 2023-04-13 05:52:11 Age [y:d:h:m:s]: 01:230:06:06:44
Block: 737485 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 426053 RingCT/type: yes/0
Extra: 011a128dcc29c0ce6bc99f49ec5e1503dc4d82ddb4ab8e1e7594863ff7c60da00c021100000001b3164c24000000000000000000

1 output(s) for total of 2.210071234000 dcy

stealth address amount amount idx
00: d46b0f2704506ac022b986b7c86e54f9fb77908fc899216a73965d14bec5c7da 2.210071234000 1184044 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": 737495, "vin": [ { "gen": { "height": 737485 } } ], "vout": [ { "amount": 2210071234, "target": { "key": "d46b0f2704506ac022b986b7c86e54f9fb77908fc899216a73965d14bec5c7da" } } ], "extra": [ 1, 26, 18, 141, 204, 41, 192, 206, 107, 201, 159, 73, 236, 94, 21, 3, 220, 77, 130, 221, 180, 171, 142, 30, 117, 148, 134, 63, 247, 198, 13, 160, 12, 2, 17, 0, 0, 0, 1, 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