Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74414e48fdec2bdfe4348a28120e265179718f27bea71b4af7a893c1c2e63fa7

Tx prefix hash: fd3fe046dfe0996401b3b354b9b956794cd61006d8195eec13087811dbfb0949
Tx public key: d10dddf5f1cbf8631c5d007aa673f2735d9383b722e66c7c1b0e19eda2a01023
Timestamp: 1700109401 Timestamp [UCT]: 2023-11-16 04:36:41 Age [y:d:h:m:s]: 01:145:07:17:51
Block: 892650 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365038 RingCT/type: yes/0
Extra: 01d10dddf5f1cbf8631c5d007aa673f2735d9383b722e66c7c1b0e19eda2a0102302110000000175e3f0e9000000000000000000

1 output(s) for total of 0.676518983000 dcy

stealth address amount amount idx
00: fef414f994fb5641f710586305763493670dd12b6e21400524fd45c80272223b 0.676518983000 1348773 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": 892660, "vin": [ { "gen": { "height": 892650 } } ], "vout": [ { "amount": 676518983, "target": { "key": "fef414f994fb5641f710586305763493670dd12b6e21400524fd45c80272223b" } } ], "extra": [ 1, 209, 13, 221, 245, 241, 203, 248, 99, 28, 93, 0, 122, 166, 115, 242, 115, 93, 147, 131, 183, 34, 230, 108, 124, 27, 14, 25, 237, 162, 160, 16, 35, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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