Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69395d47f948bd195c84deec782199040a7dce9feaa2954bbc75bbc66c786ba6

Tx prefix hash: e249eb26439b927597d70ad6ef1d62640e1571a307aa56b44ed5de53aa0c4ed4
Tx public key: 98221e3dc56a6a1009a7e16377d40bd3b6c1d8e4d47412b0669e4a76b0a77956
Timestamp: 1723870001 Timestamp [UCT]: 2024-08-17 04:46:41 Age [y:d:h:m:s]: 01:168:14:00:21
Block: 1089644 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378873 RingCT/type: yes/0
Extra: 0198221e3dc56a6a1009a7e16377d40bd3b6c1d8e4d47412b0669e4a76b0a77956021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45a99d5f52378f7e28e31559f856e429f655408ac44010821b4934a23477667c 0.600000000000 1564267 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": 1089654, "vin": [ { "gen": { "height": 1089644 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45a99d5f52378f7e28e31559f856e429f655408ac44010821b4934a23477667c" } } ], "extra": [ 1, 152, 34, 30, 61, 197, 106, 106, 16, 9, 167, 225, 99, 119, 212, 11, 211, 182, 193, 216, 228, 212, 116, 18, 176, 102, 158, 74, 118, 176, 167, 121, 86, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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