Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff42d92ddfdd735a6d4abdc0701699f968fe4869607b0379b08039a4f7ac2eed

Tx prefix hash: 5c2e996de761ceb006d2129634d8946a717054e435e4b4f7e60dcdd050284f7f
Tx public key: d1a2545598fef71a7916e924daed886cdcb1e8f71ecd2e4c5c8372c51dbb268d
Timestamp: 1676955812 Timestamp [UCT]: 2023-02-21 05:03:32 Age [y:d:h:m:s]: 02:099:02:11:24
Block: 701574 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 592464 RingCT/type: yes/0
Extra: 01d1a2545598fef71a7916e924daed886cdcb1e8f71ecd2e4c5c8372c51dbb268d02110000000174b6d784000000000000000000

1 output(s) for total of 2.906658512000 dcy

stealth address amount amount idx
00: b16b35609f651b44bd3062b17d5beba51c9eef6ec40740135154e557851f964b 2.906658512000 1145061 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": 701584, "vin": [ { "gen": { "height": 701574 } } ], "vout": [ { "amount": 2906658512, "target": { "key": "b16b35609f651b44bd3062b17d5beba51c9eef6ec40740135154e557851f964b" } } ], "extra": [ 1, 209, 162, 84, 85, 152, 254, 247, 26, 121, 22, 233, 36, 218, 237, 136, 108, 220, 177, 232, 247, 30, 205, 46, 76, 92, 131, 114, 197, 29, 187, 38, 141, 2, 17, 0, 0, 0, 1, 116, 182, 215, 132, 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