Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1c6e22de521ee4fb5bbcd27385fcf63ec3fccb563bd31060e18a37db5429316

Tx prefix hash: 7f00a7b67fa5b7bddb0d5cafbd51f56483edefa58a68b8024ec253d41b4fd320
Tx public key: 86a380a739f8fce152eaf22f70e016aa1e8b34b8547d83a1daa350e2427b20c9
Timestamp: 1693494530 Timestamp [UCT]: 2023-08-31 15:08:50 Age [y:d:h:m:s]: 02:065:19:37:10
Block: 837989 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 566748 RingCT/type: yes/0
Extra: 0186a380a739f8fce152eaf22f70e016aa1e8b34b8547d83a1daa350e2427b20c902110000000433af99f4000000000000000000

1 output(s) for total of 1.026584379000 dcy

stealth address amount amount idx
00: c34b5662cf941e5c36f20e61110ed929fc4eefcb7f63a025f4508cdf490f7fae 1.026584379000 1290679 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": 837999, "vin": [ { "gen": { "height": 837989 } } ], "vout": [ { "amount": 1026584379, "target": { "key": "c34b5662cf941e5c36f20e61110ed929fc4eefcb7f63a025f4508cdf490f7fae" } } ], "extra": [ 1, 134, 163, 128, 167, 57, 248, 252, 225, 82, 234, 242, 47, 112, 224, 22, 170, 30, 139, 52, 184, 84, 125, 131, 161, 218, 163, 80, 226, 66, 123, 32, 201, 2, 17, 0, 0, 0, 4, 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