Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 92b909d6661385b72486a90dc60108ccc2e83a79bc61a6760a9c488a4c77805d

Tx prefix hash: bac7eb3ea86e6f4816fb0efb37e2f9ac6d4b45e5c2c6bca81e2efb609f582002
Tx public key: 5915864ad0dbe4fbb46249b7af5726383a3c70467355ef0f7acae878fb39bfe6
Timestamp: 1673060062 Timestamp [UCT]: 2023-01-07 02:54:22 Age [y:d:h:m:s]: 02:101:09:00:22
Block: 669256 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 594146 RingCT/type: yes/0
Extra: 015915864ad0dbe4fbb46249b7af5726383a3c70467355ef0f7acae878fb39bfe602110000000533af99f4000000000000000000

1 output(s) for total of 3.719435304000 dcy

stealth address amount amount idx
00: 4be501c3df0bca1ad099e2115b3b7bce230a35bdccec6692347c9ec1e342814f 3.719435304000 1110559 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": 669266, "vin": [ { "gen": { "height": 669256 } } ], "vout": [ { "amount": 3719435304, "target": { "key": "4be501c3df0bca1ad099e2115b3b7bce230a35bdccec6692347c9ec1e342814f" } } ], "extra": [ 1, 89, 21, 134, 74, 208, 219, 228, 251, 180, 98, 73, 183, 175, 87, 38, 56, 58, 60, 112, 70, 115, 85, 239, 15, 122, 202, 232, 120, 251, 57, 191, 230, 2, 17, 0, 0, 0, 5, 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