Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ab7f7095880898bf0d1f5a9228cf08faa281462e053af30e0c013a436a1ca05

Tx prefix hash: 842f205258bf1cbeff26c04fa560d3a84a7a3885b563ccb17e0cddfd2e64b2c6
Tx public key: c7ef05a49870552c13eb3426ef4d98ed0af583fe2484f561c908dfd68f6c368b
Timestamp: 1704646082 Timestamp [UCT]: 2024-01-07 16:48:02 Age [y:d:h:m:s]: 01:017:13:57:44
Block: 930248 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273866 RingCT/type: yes/0
Extra: 01c7ef05a49870552c13eb3426ef4d98ed0af583fe2484f561c908dfd68f6c368b0211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ec51a87d893de4872efe1aacd23d4b11d3ca1abddc1c0820f058b182a84a647f 0.600000000000 1388130 of 15

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": 930258, "vin": [ { "gen": { "height": 930248 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec51a87d893de4872efe1aacd23d4b11d3ca1abddc1c0820f058b182a84a647f" } } ], "extra": [ 1, 199, 239, 5, 164, 152, 112, 85, 44, 19, 235, 52, 38, 239, 77, 152, 237, 10, 245, 131, 254, 36, 132, 245, 97, 201, 8, 223, 214, 143, 108, 54, 139, 2, 17, 0, 0, 0, 9, 122, 156, 244, 199, 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