Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10ed110ec4ae949c0f97431781c8ff0ec2147ef5018b32a8cab7744a47917347

Tx prefix hash: f2b5a039207de187217fab4c66526ecaac74d7c28915a717574dcec24db803b9
Tx public key: 4638d1fbee6370c594412970d7b88a1810dcd5e5e70ca4bc9902111c2b7eefc6
Timestamp: 1582103831 Timestamp [UCT]: 2020-02-19 09:17:11 Age [y:d:h:m:s]: 05:015:16:16:56
Block: 68061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1164283 RingCT/type: yes/0
Extra: 014638d1fbee6370c594412970d7b88a1810dcd5e5e70ca4bc9902111c2b7eefc60211000000084943cd9f000000000000000000

1 output(s) for total of 365.169052444000 dcy

stealth address amount amount idx
00: 79e4a6fa2fcf71d9b8af73ff459f7e012a17dc4d94f71ac944215e08e3900eff 365.169052444000 125379 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": 68071, "vin": [ { "gen": { "height": 68061 } } ], "vout": [ { "amount": 365169052444, "target": { "key": "79e4a6fa2fcf71d9b8af73ff459f7e012a17dc4d94f71ac944215e08e3900eff" } } ], "extra": [ 1, 70, 56, 209, 251, 238, 99, 112, 197, 148, 65, 41, 112, 215, 184, 138, 24, 16, 220, 213, 229, 231, 12, 164, 188, 153, 2, 17, 28, 43, 126, 239, 198, 2, 17, 0, 0, 0, 8, 73, 67, 205, 159, 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